[Touch-packages] [Bug 1581626] Re: Switching to USB sound device stops USB mouse clicks from registering

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

Title:
  Switching to USB sound device stops USB mouse clicks from registering

Status in xorg package in Ubuntu:
  New

Bug description:
  When I switch the primary sound device to a USB headset connected to
  my laptop, mouse click events no longer work except in the Sound
  Settings window.  This does not seem to occur when the device is
  connected, only when it is made the default audio device.

  Once this occurs, the mouse events do not work until the device is
  disconnected.  Clicks inside the Sound Settings window are registered
  (including buttons and other tabs inside the System Settings window,
  but not the titlebar or close/minimize/maximize buttons.)  Focus can
  be given to other windows via alt-tab and keyboard input continues to
  function, but mouse events do not register on windows focused in this
  way.

  This is *deeply* weird, BTW.

  Hardware:
  Jabra EVOLVE 80 headset
  lsusb reports: Bus 002 Device 022: ID 0b0e:0305 GN Netcom 

  Steps to reproduce:
  1. Connect the device to a USB port.
  2. Open Sound Settings window.
  3. Select the Jabra USB device as the primary sound device.
  4. Observe that mouse clicks no longer register outside of the System 
Settings window.

  dmesg shows the following during this process:

  [130169.130542] usb 2-2.1.1: new full-speed USB device number 22 using 
xhci_hcd
  [130169.223026] usb 2-2.1.1: New USB device found, idVendor=0b0e, 
idProduct=0305
  [130169.223031] usb 2-2.1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [130169.223034] usb 2-2.1.1: Product: Jabra EVOLVE LINK MS
  [130169.223036] usb 2-2.1.1: Manufacturer: GN Netcom A/S
  [130169.223038] usb 2-2.1.1: SerialNumber: 51E7669007
  [130169.225586] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.227472] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.248162] input: GN Netcom A/S Jabra EVOLVE LINK MS as 
/devices/pci:00/:00:14.0/usb2/2-2/2-2.1/2-2.1.1/2-2.1.1:1.3/0003:0B0E:0305.0013/input/input34
  [130169.302858] hid-generic 0003:0B0E:0305.0013: input,hiddev0,hidraw5: USB 
HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on 
usb-:00:14.0-2.1.1/input3
  [130169.351940] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.352187] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.358162] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.358439] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.361073] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.361323] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.373535] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.373904] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.380322] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.380645] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130177.637403] usb 2-2.1.1: USB disconnect, device number 22

  
  This appears to possibly be related to bug #1371853.

  I'm happy to provide more information, try custom kernels, etc. as
  needed.  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 13:00:25 2016
  DistUpgraded: 2016-04-25 16:22:59,827 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-35-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   i915-4.3.3-4.2.0, 2, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-10-03 (222 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=21920f07-2445-42e9-82fe-5d6b209d8688 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 

[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

[Rolf Leggewie]

bug 1674765 and https://askubuntu.com/questions/92349/how-do-i-hide-a
-particular-user-from-the-login-screen have information how to deal with
this

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

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

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

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

[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

[Rolf Leggewie]

Why am I seeing this in a bionic fresh install when I did not see this in 
trusty?
How can I workaround this very annoying and very old bug?

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

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

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

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

[Touch-packages] [Bug 1771917] Re: com.ubuntu.apport-gtk-root

[Robin Bitton]

help me get rid of this error box, comes up everytime.  I was trying to
get access to adobe to download some coupons and I think that caused the
problem.  I still can't load adobe to print.

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

Title:
  com.ubuntu.apport-gtk-root

Status in xorg package in Ubuntu:
  New

Bug description:
  com.ubuntu.apport-gtk-root

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  NonfreeKernelModules: wl
  .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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 17 22:36:12 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics 
Controller [1179:f931]
  InstallationDate: Installed on 2016-04-21 (756 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite L70-B
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=f8cee356-0708-45ca-8480-9665f2b427ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.20
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.20:bd05/27/2014:svnTOSHIBA:pnSatelliteL70-B:pvrPSKRLC-00Y00G:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L70-B
  dmi.product.version: PSKRLC-00Y00G
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-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: Thu May 17 22:29:19 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20555 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1771917] [NEW] com.ubuntu.apport-gtk-root

[Robin Bitton]

Public bug reported:

com.ubuntu.apport-gtk-root

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
NonfreeKernelModules: wl
.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: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu May 17 22:36:12 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics 
Controller [1179:f931]
InstallationDate: Installed on 2016-04-21 (756 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: TOSHIBA Satellite L70-B
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=f8cee356-0708-45ca-8480-9665f2b427ff ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.20
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.20:bd05/27/2014:svnTOSHIBA:pnSatelliteL70-B:pvrPSKRLC-00Y00G:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L70-B
dmi.product.version: PSKRLC-00Y00G
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-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: Thu May 17 22:29:19 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   20555 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  com.ubuntu.apport-gtk-root

Status in xorg package in Ubuntu:
  New

Bug description:
  com.ubuntu.apport-gtk-root

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  NonfreeKernelModules: wl
  .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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 17 22:36:12 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics 
Controller [1179:f931]
  InstallationDate: Installed on 2016-04-21 (756 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite L70-B
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=f8cee356-0708-45ca-8480-9665f2b427ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.20
  

[Touch-packages] [Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04

[Wes]

> A simple "apt install ifupdown" will not undo everything that
installer has done to setup the system, nor redo it for the alternative
networking management tool. Where do you expect ifupdown configs to
materialize from?

Well that's kind of my point - your documentation is deficient around
that.  And we expect the ifupdown configuration to 'materialize' from
the sysadmin writing them, that's the point of ifupdown isn't it?  I'd
wager that anyone reverting to ifupdown is doing so specifically because
they don't want something managing configuration for them - they want to
do it themselves.


> Given that the system is sensitive to all configs present on disk. This is 
> similar situation to how on the desktop one cannot simply "remove 
> network-manager & install ifupdown" to switch to ifupdown.

That's why we tried disabling systemd-networkd, which came back as
enabled on subsequent boots.  Apparently netplan adds some hooks that
aren't clearly documented (at least when I looked on netplan.io, maybe I
missed them?).  I guess netplan needs to be actively purged, but that
breaks the dep on it in ubuntu-minimal which may not be desirable to
purge if its dep list changes in the future and people want to pull in
those deps (apart from netplan).


> can you please give the examples that you have experienced, specifically? the 
> ubuntu developers have gone extensive amount of porting, and integration 
> testing to ensure that as many things as possible are fixed to work, both on 
> new installs and upgrades.

We run gateways and firewalls with multiple providers and so forth.  The
need for pre-up, and more importantly post-up, comes up frequently in
all sorts of situations.  'We need to (re)start openvpn after this vlan
interface is configured, but both need to happen only after this pppoe
interface is (re)configured' (yeah some of our ISPs still use ppp.. even
on fibre links.  it's terrible).  This is why systemd-networkd
implements such a facility, and why ifupdown does too.  I feel it's
near-sighted of netplan to pretend the need doesn't exist when the
things it's configuring do see the need and do implement such
facilities.  If Ubuntu devs tested netplan extensively' I'd wager they
never tested beyond basic use cases otherwise the deficiency would have
been obvious.  There are other, complex configurations out in the wild
and netplan can't even begin to accommodate them in its current form.
Which is fine...  we remove it.  But removing it appears to be
problematic, or not permanent.  So what's the correct method?  Remove
the initial config the installer makes?  Does that let systemd-networkd
remain disabled or does it get re-enabled anyway?  Can you put this
somewhere in the documentation and /etc/network/interfaces comments
beyond the mere 'apt install ifupdown' that is there currently?  As a
side note we found an issue yesterday where DHCP via systemd-networkd in
18.04 wasn't working against an isc-dhcpd running on an early ubuntu
version.  The apparent inability to prevent systemd-networkd from trying
to run and conflicting with other mechanisms was causing enough grief
for my employer to decide to just give 18.04 a miss entirely. :(  I
could have put more time in to diagnosing it, or testing netplan with no
config and purging the previous config from systemd-networkd and
rebooting and hoping networkd didn't come back but it had already cost
enough time by then and he made the call.


> Please provide the contents of /etc/netplan on the affected systems, and 
> please let me know, if removing files in said directory makes networkd ignore 
> interfaces.

I'll test this when I have a spare minute and report back soon

Thanks,
Wes

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

Title:
  forced use of systemd-networkd interferes with ifupdown in 18.04

Status in ifupdown package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For several reasons, we are not able to use netplan nor systemd-
  networkd due to legacy applications that expect ifupdown's pre-up and
  post-up script mechanism.  The documentation around 18.04's
  (premature, I feel) wholesale adoption of netplan claims that one can
  revert to old behaviour by merely installing ifupdown (amongst
  assertions that netplan will never offer a mechanism for configuring
  pre-up and post-up actions even for network managers that support
  them).

  However when ifupdown is installed, systemd-networkd still tries to
  manage interfaces.  If you 'systemctl disable systemd-networkd', upon
  next reboot it is automatically re-enabled.  We tried disabling any
  systemd units even remotely related to networking and yet systemd-
  networkd still runs.  If it hasn't been configured, it tries to DHCP.
  On networks that don't provide DHCP this results in a stupendously
  long stall 

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Gmgarciam]

Hello. My situation was very complicated, and none of the fixes I found
would work. I am running a Nvidia GTX970 with an Intel CPU and using a
dual monitor setup. Ubuntu 17.04 was working very well. Later upgrading
to Ubuntu 17.10, the Nvidia graphics became an issue because of Wayland,
but I followed this guide and was able to set it working for 17.10,
https://charlienewey.github.io/getting-nvidia-drivers-working-on-
ubuntu-17-10/ . For 18.04, nothing I found online was working. I was
able to setup Openbox and use that to investigate the matter. I
suspected it was some sort of opengl problem since all applications
requiring it would fail to run and cheking with the terminal, it would
say that the libGLU1.1.so was not found, or one of those opengl
libraries. Upon further investigating, it turned out that the xorg that
comes stock with 18.04 does not have the latest Mesa patch that supports
nvidia graphics cards. So I ended up getting the padoka ppa in order to
get the latest xorg and mesa. Upon doing so, everything is working fine.
I thought this fix was a little unorthodox being that I believed that
Padoka was for Nouvou and AMD cards but, apparently it fixed the issue
with the proprietary 396 drivers. I had the same issue with the 384, and
390. So I am not sure if this fix only pertains to the Nvidia 396
drivers, but I believe the problem stems from an Xorg that does not have
the latest Mesa.

https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[mike stewart]

This seems to affect many public Wifi Hotspots. A very common example is
the new setup by Starbucks/Google (usually seen as **Google Starbucks
Wifi**) in the US by (Tech behind it is https://globalreachtech.com/
with their http://odyssys.net/).

Under Ubuntu 16.04, Windows, Android, Mac OS, or iPhone, a WiFi guest
user can connect without problem.  However, since upgrading to Ubuntu
18.04, I've encountered this in at least three separate Starbucks stores
in Southern California.


## WORKAROUND ##

An easier workaround, with fewer system modifications than the original
bug report is to use `ip route` to determine the IP address of the host
router, then add the hostname with that adress to `/etc/hosts`


Step by step details can be found here: https://askubuntu.com/a/1027605/139249

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[mike stewart]

** Summary changed:

- DNS cannot be resolved in Hotel Hotspot
+ DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

[Steve Langasek]

I can reproduce @earth2mark-eeepc's findings at another Starbucks.

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

Title:
  DNS cannot be resolved in Hotel Hotspot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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

[Touch-packages] [Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Brian Murray]

Hello Guilherme, or anyone else affected,

Accepted initramfs-tools into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.103ubuntu4.11 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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. 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: initramfs-tools (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-trusty

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

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

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

Bug description:
  [Impact]

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

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

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

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

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

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

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

  (lsblk output of my test env:

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

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

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

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

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

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

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

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

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

  $ rmadison initramfs-tools

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

To manage notifications about this bug go to:

[Touch-packages] [Bug 1771188] Re: Ubuntu 18.04 System hangs when logging in or rebooting. Shutdown reboots instead. Suspend wakes after suspending.

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu 18.04 System hangs when logging in or rebooting.  Shutdown
  reboots instead.  Suspend wakes after suspending.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Originally I thought the system had crashed when logging in or
  shutdown.  But it turns out it's hanging for about 60-90 seconds.
  When shutting down system will reboot instead.

  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  uname -a
  Linux bridge 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Clean install.
  Shutting down system reboots instead.
  Suspends does not stay suspended.
  Login and shutdown hangs for a long time (60-90 seconds)

  
  Seeing these in logs.

  [  197.300273] [ cut here ]
  [  197.300274] nouveau :01:00.0: timeout
  [  197.300336] WARNING: CPU: 5 PID: 1938 at 
/build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207
 gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
  [  197.300336] Modules linked in: msr thunderbolt cmac bnep nouveau ttm arc4 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev btusb btrtl media btbcm btintel bluetooth ecdh_generic nls_iso8859_1 
ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 
nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG 
xt_limit xt_tcpudp xt_addrtype snd_hda_codec_hdmi hid_multitouch 
snd_hda_codec_realtek dell_smbios_wmi snd_hda_codec_generic dell_wmi 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof mxm_wmi dell_laptop 
dell_smbios_smm dell_smbios dcdbas nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_intel xt_conntrack dell_smm_hwmon snd_hda_codec snd_hda_core intel_rapl 
snd_hwdep x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm kvm_intel kvm 
snd_seq_midi
  [  197.300373]  snd_seq_midi_event irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc snd_rawmidi ath10k_pci snd_seq ath10k_core aesni_intel 
snd_seq_device ath aes_x86_64 snd_timer crypto_simd glue_helper cryptd 
intel_cstate intel_rapl_perf ip6table_filter mac80211 ip6_tables snd 
nf_conntrack_netbios_ns nf_conntrack_broadcast input_leds joydev nf_nat_ftp 
nf_nat serio_raw cfg80211 idma64 rtsx_pci_ms virt_dma nf_conntrack_ftp memstick 
soundcore nf_conntrack mei_me intel_lpss_pci processor_thermal_device 
intel_pch_thermal shpchp mei intel_lpss intel_soc_dts_iosf libcrc32c wmi 
mac_hid int3403_thermal int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel acpi_pad tpm_crb sparse_keymap sch_fq_codel parport_pc ppdev 
lp parport iptable_filter ip_tables x_tables autofs4 i915 rtsx_pci_sdmmc
  [  197.300397]  i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt 
nvme fb_sys_fops psmouse drm nvme_core rtsx_pci ahci libahci i2c_hid hid video
  [  197.300403] CPU: 5 PID: 1938 Comm: Xorg Tainted: GW
4.15.0-20-generic #21-Ubuntu
  [  197.300404] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.9.4 
04/23/2018
  [  197.300420] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
  [  197.300420] RSP: :b8c0847e7750 EFLAGS: 00010286
  [  197.300421] RAX:  RBX: 980259b63e20 RCX: 
0006
  [  197.300422] RDX: 0007 RSI: 0086 RDI: 
98027e556490
  [  197.300422] RBP: b8c0847e7788 R08: 0001 R09: 
0b9f
  [  197.300423] R10: c0c6c6d0 R11:  R12: 
980258b66c00
  [  197.300423] R13: 98024e9b8d80 R14: 002d78c6d8c0 R15: 
980257106600
  [  197.300424] FS:  7fcbd5229600() GS:98027e54() 
knlGS:
  [  197.300425] CS:  0010 DS:  ES:  CR0: 80050033
  [  197.300426] CR2: 7fcbcb1ed000 CR3: 00085a34c004 CR4: 
003606e0
  [  197.300426] Call Trace:
  [  197.300442]  gp100_vmm_flush+0x17/0x20 [nouveau]
  [  197.300456]  nvkm_vmm_iter.constprop.13+0x2e5/0x880 [nouveau]
  [  197.300470]  ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
  [  197.300483]  ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau]
  [  197.300496]  nvkm_vmm_map+0x21e/0x400 [nouveau]
  [  197.300508]  ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
  [  197.300521]  nvkm_vram_map+0x57/0x80 [nouveau]
  [  197.300533]  gf100_mem_map+0xf8/0x180 [nouveau]
  [  197.300546]  nvkm_umem_map+0x6b/0x100 [nouveau]
  [  197.300556]  nvkm_object_map+0x1a/0x30 [nouveau]
  [  197.300565]  nvkm_ioctl_map+0x78/0xe0 [nouveau]
  [  197.300573]  nvkm_ioctl+0x11d/0x280 [nouveau]
  [  197.300590]  nvkm_client_ioctl+0x12/0x20 [nouveau]
  [  197.300597]  nvif_object_ioctl+0x47/0x50 [nouveau]
  [  197.300605]  

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

[Dan Streetman]

xenial:

root@lp1701023-x:/etc/network/interfaces.d# dpkg -l |grep ifupdown
ii  ifupdown 0.8.10ubuntu1.4
amd64high level tools to configure network interfaces
root@lp1701023-x:/etc/network/interfaces.d# dpkg -l |grep vlan
ii  vlan 1.9-3.2ubuntu1.16.04.5 
amd64user mode programs to enable VLANs on your ethernet devices

all comment 19 tests work.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1701023

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  In Progress
Status in vlan package in Ubuntu:
  Fix Released
Status in ifupdown source package in Trusty:
  Fix Committed
Status in vlan source package in Trusty:
  Fix Committed
Status in ifupdown source package in Xenial:
  Fix Committed
Status in vlan source package in Xenial:
  Fix Committed
Status in ifupdown source package in Artful:
  Fix Committed
Status in vlan source package in Artful:
  Fix Committed
Status in ifupdown source package in Bionic:
  Fix Committed
Status in vlan source package in Bionic:
  Fix Committed
Status in ifupdown package in Debian:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  [impact]

  in bug 1573272, the vlan pkg was changed to perform a full ifup inside
  its if-pre-up.d/vlan script.  This allowed correct ordering of ifup
  for a vlan and its raw-device, as previously there was a race
  condition between them (see that bug for details).

  However, this causes hangs during ifup with certain specific configs.
  The reasons are given starting in comment 13.

  The result is a regression for those using the specific ifupdown
  configs; when they try to reboot and/or ifup -a, it will hang trying
  to bring up their network, preventing boot from finishing (or hanging
  before the network is fully configured).

  [test case]

  upgrade to the latest vlan package and configure the system with an
  affected ifupdown config, then reboot.  The reboot will hang while
  trying to bring the network up.

  see the original description below for an example ifupdown config to
  reproduce this, although there are other possible configs that
  will/may trigger this regression.

  [regression potential]

  The fix for this moves the creation of the vlan(s) corresponding to a
  physical raw-device 'hotplug' event out of the udev processing path
  for the raw-device, and into an ifup post script for the raw-device
  ifup.  If this is not done correctly, then any interfaces that are
  hotplugged, and have vlans configured on them, may fail to correctly
  create/configure their vlan(s).

  This change does remove the direct call to ifup from the if-pre-up.d
  (or if-up.d) scripts, so there should not be any regression potential
  for more ifup deadlocks.

  [other info]

  this required both ifupdown and vlan to be patched.  vlan was patched
  to remove the problematic call to ifup from the vlan pre-up script,
  and add a call to create the vlan interface(s) from a new post-up
  script, as well as adding a parameter to vlan-network-interface script
  to handle the call from udev itself differently than a call from
  elsewhere (such as the if-up.d/vlan script).  this works for bootup
  and ifup/ifup -a, but fails for device hotplug because of a bug in
  ifupdown that prevents calling ifquery from an ifup script; that has
  been patched upstream already, and is the only ifupdown change needed
  here.

  
  [original description]

  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
    └─run-parts,1501 /etc/network/if-pre-up.d
    └─bridge,1502 /etc/network/if-pre-up.d/bridge
    └─bridge,1508 /etc/network/if-pre-up.d/bridge
    └─vlan,1511 /etc/network/if-pre-up.d/vlan
    └─ifup,1532 eth0

  
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
    address 192.168.10.65
    netmask 255.255.255.192
    gateway 192.168.10.66

  auto eth0.11
    address 192.168.11.1
    netmask 255.255.255.0

  auto br1134
  iface br1134 inet manual
    bridge_ports eth0.1134
    bridge_stp off
    bridge_fd 0
  

  The underlying interface eth0.1134 is not explicitly defined, but was
  previously auto-created during "ifup -a" execution. This apparently
  fails now.

  Reverting back to the 10.1 version re-establishes old behavior.

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

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

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

[Dan Streetman]

tested on artful with:

root@lp1701023-a:~# dpkg -l | grep ifupdown
ii  ifupdown   0.8.16ubuntu2.1  
amd64high level tools to configure network interfaces
root@lp1701023-a:~# dpkg -l | grep vlan
ii  vlan   1.9-3.2ubuntu5.17.10.1   
amd64user mode programs to enable VLANs on your ethernet 
devices


all tests from comment 19 work.  as the previous versions also all worked, no 
need to test them again.

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  In Progress
Status in vlan package in Ubuntu:
  Fix Released
Status in ifupdown source package in Trusty:
  Fix Committed
Status in vlan source package in Trusty:
  Fix Committed
Status in ifupdown source package in Xenial:
  Fix Committed
Status in vlan source package in Xenial:
  Fix Committed
Status in ifupdown source package in Artful:
  Fix Committed
Status in vlan source package in Artful:
  Fix Committed
Status in ifupdown source package in Bionic:
  Fix Committed
Status in vlan source package in Bionic:
  Fix Committed
Status in ifupdown package in Debian:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  [impact]

  in bug 1573272, the vlan pkg was changed to perform a full ifup inside
  its if-pre-up.d/vlan script.  This allowed correct ordering of ifup
  for a vlan and its raw-device, as previously there was a race
  condition between them (see that bug for details).

  However, this causes hangs during ifup with certain specific configs.
  The reasons are given starting in comment 13.

  The result is a regression for those using the specific ifupdown
  configs; when they try to reboot and/or ifup -a, it will hang trying
  to bring up their network, preventing boot from finishing (or hanging
  before the network is fully configured).

  [test case]

  upgrade to the latest vlan package and configure the system with an
  affected ifupdown config, then reboot.  The reboot will hang while
  trying to bring the network up.

  see the original description below for an example ifupdown config to
  reproduce this, although there are other possible configs that
  will/may trigger this regression.

  [regression potential]

  The fix for this moves the creation of the vlan(s) corresponding to a
  physical raw-device 'hotplug' event out of the udev processing path
  for the raw-device, and into an ifup post script for the raw-device
  ifup.  If this is not done correctly, then any interfaces that are
  hotplugged, and have vlans configured on them, may fail to correctly
  create/configure their vlan(s).

  This change does remove the direct call to ifup from the if-pre-up.d
  (or if-up.d) scripts, so there should not be any regression potential
  for more ifup deadlocks.

  [other info]

  this required both ifupdown and vlan to be patched.  vlan was patched
  to remove the problematic call to ifup from the vlan pre-up script,
  and add a call to create the vlan interface(s) from a new post-up
  script, as well as adding a parameter to vlan-network-interface script
  to handle the call from udev itself differently than a call from
  elsewhere (such as the if-up.d/vlan script).  this works for bootup
  and ifup/ifup -a, but fails for device hotplug because of a bug in
  ifupdown that prevents calling ifquery from an ifup script; that has
  been patched upstream already, and is the only ifupdown change needed
  here.

  
  [original description]

  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
    └─run-parts,1501 /etc/network/if-pre-up.d
    └─bridge,1502 /etc/network/if-pre-up.d/bridge
    └─bridge,1508 /etc/network/if-pre-up.d/bridge
    └─vlan,1511 /etc/network/if-pre-up.d/vlan
    └─ifup,1532 eth0

  
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
    address 192.168.10.65
    netmask 255.255.255.192
    gateway 192.168.10.66

  auto eth0.11
    address 192.168.11.1
    netmask 255.255.255.0

  auto br1134
  iface br1134 inet manual
    bridge_ports eth0.1134
    bridge_stp off
    bridge_fd 0
  

  The underlying interface eth0.1134 is not explicitly defined, but was
  previously auto-created during "ifup -a" execution. This apparently
  fails now.

  Reverting back to the 10.1 version re-establishes old behavior.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

[Dan Streetman]

tested bionic per comment 19 with:

root@lp1701023-b:~# dpkg -l | grep ifupdown
ii  ifupdown 0.8.17ubuntu1 amd64
high level tools to configure network interfaces
root@lp1701023-b:~# dpkg -l | grep vlan
ii  vlan 1.9-3.2ubuntu5amd64
user mode programs to enable VLANs on your ethernet devices

and with:

root@lp1701023-b:~# dpkg -l | grep ifupdown
ii  ifupdown 0.8.17ubuntu1.1   amd64
high level tools to configure network interfaces
root@lp1701023-b:~# dpkg -l | grep vlan
ii  vlan 1.9-3.2ubuntu6amd64
user mode programs to enable VLANs on your ethernet devices


all tests from comment 19 do work with both package versions.

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

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

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  In Progress
Status in vlan package in Ubuntu:
  Fix Released
Status in ifupdown source package in Trusty:
  Fix Committed
Status in vlan source package in Trusty:
  Fix Committed
Status in ifupdown source package in Xenial:
  Fix Committed
Status in vlan source package in Xenial:
  Fix Committed
Status in ifupdown source package in Artful:
  Fix Committed
Status in vlan source package in Artful:
  Fix Committed
Status in ifupdown source package in Bionic:
  Fix Committed
Status in vlan source package in Bionic:
  Fix Committed
Status in ifupdown package in Debian:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  [impact]

  in bug 1573272, the vlan pkg was changed to perform a full ifup inside
  its if-pre-up.d/vlan script.  This allowed correct ordering of ifup
  for a vlan and its raw-device, as previously there was a race
  condition between them (see that bug for details).

  However, this causes hangs during ifup with certain specific configs.
  The reasons are given starting in comment 13.

  The result is a regression for those using the specific ifupdown
  configs; when they try to reboot and/or ifup -a, it will hang trying
  to bring up their network, preventing boot from finishing (or hanging
  before the network is fully configured).

  [test case]

  upgrade to the latest vlan package and configure the system with an
  affected ifupdown config, then reboot.  The reboot will hang while
  trying to bring the network up.

  see the original description below for an example ifupdown config to
  reproduce this, although there are other possible configs that
  will/may trigger this regression.

  [regression potential]

  The fix for this moves the creation of the vlan(s) corresponding to a
  physical raw-device 'hotplug' event out of the udev processing path
  for the raw-device, and into an ifup post script for the raw-device
  ifup.  If this is not done correctly, then any interfaces that are
  hotplugged, and have vlans configured on them, may fail to correctly
  create/configure their vlan(s).

  This change does remove the direct call to ifup from the if-pre-up.d
  (or if-up.d) scripts, so there should not be any regression potential
  for more ifup deadlocks.

  [other info]

  this required both ifupdown and vlan to be patched.  vlan was patched
  to remove the problematic call to ifup from the vlan pre-up script,
  and add a call to create the vlan interface(s) from a new post-up
  script, as well as adding a parameter to vlan-network-interface script
  to handle the call from udev itself differently than a call from
  elsewhere (such as the if-up.d/vlan script).  this works for bootup
  and ifup/ifup -a, but fails for device hotplug because of a bug in
  ifupdown that prevents calling ifquery from an ifup script; that has
  been patched upstream already, and is the only ifupdown change needed
  here.

  
  [original description]

  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
    └─run-parts,1501 /etc/network/if-pre-up.d
    └─bridge,1502 /etc/network/if-pre-up.d/bridge
    └─bridge,1508 /etc/network/if-pre-up.d/bridge
    └─vlan,1511 /etc/network/if-pre-up.d/vlan
    └─ifup,1532 eth0

  
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
    address 192.168.10.65
    netmask 255.255.255.192
    gateway 192.168.10.66

  auto eth0.11
    address 192.168.11.1
    netmask 255.255.255.0

  auto br1134
  iface br1134 inet manual
    bridge_ports eth0.1134
    bridge_stp off
    bridge_fd 0
  

  The underlying interface eth0.1134 is 

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Bernadette Addison]

also, still investigating.  every one of these fixes all lead to the
same outcome for me - cannot boot with nvidia proprietary drivers
installed, or else stuck in a boot-loop after entering password at gdm
screen.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

-- 
Mailing list: https://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 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols

[Matthias Klose]

On 17.05.2018 16:03, alamaral wrote:
> The problem is that most system library code is built
> without -g, so gdb doesn't have whatever information is necessary to
> unwind the stack properly.

this is wrong. every package is built with -g, however the debug symbols are
split out into separate -dbg or dbgsym packages.

> It seems that gcc, with the -g option, adds .cfi directives into the
> assembler code, and gdb needs that info.  Remove the .cfi directives and
> you get the "Backtrace stopped: previous frame identical to this frame
> (corrupt stack?)" error.
> 
> Even a very simple program with subroutine calls (similar to below) will
> exhibit this problem:
> 
> void foo(int i)
> {
> if (i < 100) foo(i+1);
> printf("i=%d\n", i);
> }
> 
> main()
> {
> foo(0);
> }
> 
> When compiled without -g each time the program calls foo the stack looks
> to gdb like it's corrupted, and only the topmost level is shown, along
> with the error.  Compile with -g and everything works, at least until
> you step into printf, which wasn't compiled with -g.
> 
> Once you step out of printf you'll get your stack back.
> 
> This feels like a compiler bug to me, i.e. gcc __SHOULD__ generate at
> least the minimal set of .cfi directives that are needed for gdb to
> generate a backtrace, regardless of whether -g is specified or not.

is gdb using the split out debug symbols for your use case?

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

Title:
  gdb reports 'corrupt stack' on armhf without symbols

Status in Linaro GDB:
  New
Status in gdb package in Ubuntu:
  Triaged

Bug description:
  [Test Case]
  sleep 120 &
  kill -SEGV %1

  Observe a corrupt stack in the generated crash file.

  Original Report
  ---
  On armhf crash files fail to retrace and gdb reports 'corrupt stack' errors

  For example bug 1323241
  Thread 1 (Thread 0xb0b3b450 (LWP 2243)):
  #0  0x0030 in ?? ()
  No symbol table info available.
  #1  0xa9990cbe in ?? () from 
/usr/lib/arm-linux-gnueabihf/unity8/qml/Unity/Launcher/libUnityLauncher-qml.so
  No symbol table info available.
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  I also tried directly on the device to run an unstripped and stripped
  build of cat and gdb fails to unwind the stack when the binary is
  stripped. The result of this test is:

  == unstripped ==
  Reading symbols from ./cat...done.
  (gdb) run
  Starting program: /home/phablet/tmp/coreutils-8.21/src/cat
  ^C
  Program received signal SIGINT, Interrupt.
  0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb648 in read (__nbytes=65536, __buf=0x19000, __fd=0) at 
/usr/include/arm-linux-gnueabihf/bits/unistd.h:44
  #2  safe_read (fd=0, buf=buf@entry=0x19000, count=count@entry=65536) at 
lib/safe-read.c:66
  #3  0x9ace in simple_cat (bufsize=65536, buf=0x19000 "") at src/cat.c:168
  #4  main (argc=1, argv=) at src/cat.c:730
  (gdb) quit

  == stripped ==
  Reading symbols from ./cat...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /home/phablet/tmp/coreutils-8.21/src/cat
  ^C
  Program received signal SIGINT, Interrupt.
  0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb648 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  I'd expect the same number of frames and addresses when the binary is
  stripped or not with '??' instead of names when it is stripped.

  ProblemType: BugDistroRelease: Ubuntu 14.10
  Package: gdb (not installed)
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Mon Jun  2 11:07:07 2014
  InstallationDate: Installed on 2014-06-02 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140602)SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols

[alamaral]

Don't know if anyone is still working on this problem (i.e. corrupt
stack on arm in gdb), but I've found a solution.  Any code that is
compiled with -g seems to work fine with gdb, as far as generating a
backtrace.  The problem is that most system library code is built
without -g, so gdb doesn't have whatever information is necessary to
unwind the stack properly.

It seems that gcc, with the -g option, adds .cfi directives into the
assembler code, and gdb needs that info.  Remove the .cfi directives and
you get the "Backtrace stopped: previous frame identical to this frame
(corrupt stack?)" error.

Even a very simple program with subroutine calls (similar to below) will
exhibit this problem:

void foo(int i)
{
if (i < 100) foo(i+1);
printf("i=%d\n", i);
}

main()
{
foo(0);
}

When compiled without -g each time the program calls foo the stack looks
to gdb like it's corrupted, and only the topmost level is shown, along
with the error.  Compile with -g and everything works, at least until
you step into printf, which wasn't compiled with -g.

Once you step out of printf you'll get your stack back.

This feels like a compiler bug to me, i.e. gcc __SHOULD__ generate at
least the minimal set of .cfi directives that are needed for gdb to
generate a backtrace, regardless of whether -g is specified or not.

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

Title:
  gdb reports 'corrupt stack' on armhf without symbols

Status in Linaro GDB:
  New
Status in gdb package in Ubuntu:
  Triaged

Bug description:
  [Test Case]
  sleep 120 &
  kill -SEGV %1

  Observe a corrupt stack in the generated crash file.

  Original Report
  ---
  On armhf crash files fail to retrace and gdb reports 'corrupt stack' errors

  For example bug 1323241
  Thread 1 (Thread 0xb0b3b450 (LWP 2243)):
  #0  0x0030 in ?? ()
  No symbol table info available.
  #1  0xa9990cbe in ?? () from 
/usr/lib/arm-linux-gnueabihf/unity8/qml/Unity/Launcher/libUnityLauncher-qml.so
  No symbol table info available.
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  I also tried directly on the device to run an unstripped and stripped
  build of cat and gdb fails to unwind the stack when the binary is
  stripped. The result of this test is:

  == unstripped ==
  Reading symbols from ./cat...done.
  (gdb) run
  Starting program: /home/phablet/tmp/coreutils-8.21/src/cat
  ^C
  Program received signal SIGINT, Interrupt.
  0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb648 in read (__nbytes=65536, __buf=0x19000, __fd=0) at 
/usr/include/arm-linux-gnueabihf/bits/unistd.h:44
  #2  safe_read (fd=0, buf=buf@entry=0x19000, count=count@entry=65536) at 
lib/safe-read.c:66
  #3  0x9ace in simple_cat (bufsize=65536, buf=0x19000 "") at src/cat.c:168
  #4  main (argc=1, argv=) at src/cat.c:730
  (gdb) quit

  == stripped ==
  Reading symbols from ./cat...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /home/phablet/tmp/coreutils-8.21/src/cat
  ^C
  Program received signal SIGINT, Interrupt.
  0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb6f6e914 in read () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb648 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  I'd expect the same number of frames and addresses when the binary is
  stripped or not with '??' instead of names when it is stripped.

  ProblemType: BugDistroRelease: Ubuntu 14.10
  Package: gdb (not installed)
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Mon Jun  2 11:07:07 2014
  InstallationDate: Installed on 2014-06-02 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140602)SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1753333] Update Released

[Łukasz Zemczak]

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Currently, the Additional Drivers tool uninstalls only the driver package 
that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that 
package is only a meta-package. Removing the meta-package will not uninstall 
the driver.

  We should make sure to uninstall all its nvidia related dependencies,
  not only the meta-package.

  [Test Case]
  1) Open the "Software & Updates" app, and select the "Additional Drivers" tab

  2) Uninstall the NVIDIA 390 driver

  3) Check that, for example, the nvidia-dkms-390 package was
  uninstalled:

  apt-cache policy nvidia-dkms-390

  The package will be reported as installed, because the current code
  didn't remove it.

  [Regression Potential]
  Relatively low, as the change in behaviour only affects the nvidia driver, 
and it only causes the Additional Drivers tool to remove dependencies of the 
meta-package that have the "nvidia" string in their name.

  __
  When you are in the initial install state, you can easily switch from the 
Nouvea drivers to the Nvidia drivers by choosing the option in "Software and 
Updates -> Additional Drivers".  However, when you attempt to switch back (by 
selecting the nouveau option and clicking Apply), and subsequently reboot, your 
system will still come up using the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

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

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

[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.32.2

---
software-properties (0.96.24.32.2) bionic; urgency=medium

  * SoftwarePropertiesGtk.py: uninstall the actual nvidia packages,
not only the meta-package (LP: #175).

 -- Alberto Milone   Wed, 02 May 2018
15:58:01 +0200

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Currently, the Additional Drivers tool uninstalls only the driver package 
that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that 
package is only a meta-package. Removing the meta-package will not uninstall 
the driver.

  We should make sure to uninstall all its nvidia related dependencies,
  not only the meta-package.

  [Test Case]
  1) Open the "Software & Updates" app, and select the "Additional Drivers" tab

  2) Uninstall the NVIDIA 390 driver

  3) Check that, for example, the nvidia-dkms-390 package was
  uninstalled:

  apt-cache policy nvidia-dkms-390

  The package will be reported as installed, because the current code
  didn't remove it.

  [Regression Potential]
  Relatively low, as the change in behaviour only affects the nvidia driver, 
and it only causes the Additional Drivers tool to remove dependencies of the 
meta-package that have the "nvidia" string in their name.

  __
  When you are in the initial install state, you can easily switch from the 
Nouvea drivers to the Nvidia drivers by choosing the option in "Software and 
Updates -> Additional Drivers".  However, when you attempt to switch back (by 
selecting the nouveau option and clicking Apply), and subsequently reboot, your 
system will still come up using the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

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

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

[Touch-packages] [Bug 1769891] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)

[Matthias Klose]

** Package changed: python2.7 (Ubuntu) => duplicity (Ubuntu)

** Package changed: duplicity (Ubuntu) => deja-dup (Ubuntu)

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

Title:
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
  37: ordinal not in range(128)

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Hello

  duplicity crash after backup because there is a python error

  Step to reproduce.

  1. Active developper option in software center
  2. install the backup python pyckage
  3. Lanch a backup with duplicity command

  Result :

  
   Type of backup set:Time:   Number of volumes:
  Full Tue Feb 20 22:00:34 2018  2284
   Incremental Thu Feb 22 03:26:48 2018 1
   Incremental Fri Feb 23 23:23:09 201842
   Incremental Wed Apr  4 15:54:05 2018   151
   Incremental Thu Apr  5 04:27:55 2018 1
   Incremental Sat Apr 14 21:51:41 2018 1
  -
  Also found 0 backup sets not part of any chain,
  and 1 incomplete backup set.
  These may be deleted by running duplicity with the "cleanup" command.
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Deleting /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Forgetting temporary file /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Processing remote manifest 
duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest (154)
  Found manifest volume 1
  Found 1 volumes in manifest
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 556, in 
get
  "from backend") % util.ufn(local_path.name))
   BackendException: File /tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not 
found locally after get from backend

  Attempt 1 failed. BackendException: File 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found locally after get from 
backend
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 552, in 
get
  self.backend._get(remote_filename, local_path)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 151, in _get
  self.__copy_file(source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 124, in __copy_file
  None, self.__copy_progress, None)
   Error: g-io-error-quark: Error opening file 
“/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3”: No such file or directory 
(1)

  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mkstemp-useaK1-1
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Cleanup of temporary directory /tmp/duplicity-hFkoYG-tempdir failed - this is 
probably a bug.
  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 658, in incremental_backup
  sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 539, 
in get_fileobjs
  return [filename_to_fileobj(f) for f in self.get_filenames(time)]
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 676, in 
get_fileobj_read
  self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in 
inner_retry
  util.uexc(e)), code=code, extra=extra)
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  Releasing lockfile /home/username/.cache/deja-
  dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile

  Note : this bug affect eclim and other python pyckages

  http://eclim.org

  
  Could you help me please to fix this 

[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails

[Brian Murray]

I went ahead and verified this on bionic.

Start-Date: 2018-05-17  11:32:08
Commandline: apt-get install software-properties-gtk
Requested-By: bdmurray (1000)
Upgrade: python3-software-properties:amd64 (0.96.24.32.1, 0.96.24.32.2), 
software-properties-gtk:amd64 (0.96.24.32.1, 0.96.24.32.2), 
software-properties-common:amd64 (0.96.24.32.1, 0.96.24.32.2)
End-Date: 2018-05-17  11:32:13

Start-Date: 2018-05-17  11:34:44
Commandline: aptdaemon role='role-commit-packages' sender=':1.123'
Remove: libnvidia-compute-390:amd64 (390.48-0ubuntu3), 
libnvidia-encode-390:amd64 (390.48-0ubuntu3), 
xserver-xorg-video-nvidia-390:amd64 (390.48-0ubuntu3), libnvidia-gl-390:amd64 
(390.48-0ubuntu3), libnvidia-fbc1-390:amd64 (390.48-0ubuntu3), 
libnvidia-decode-390:amd64 (390.48-0ubuntu3), libnvidia-cfg1-390:amd64 
(390.48-0ubuntu3), nvidia-utils-390:amd64 (390.48-0ubuntu3), 
nvidia-dkms-390:amd64 (390.48-0ubuntu3), nvidia-compute-utils-390:amd64 
(390.48-0ubuntu3), libnvidia-ifr1-390:amd64 (390.48-0ubuntu3), 
nvidia-driver-390:amd64 (390.48-0ubuntu3), nvidia-kernel-source-390:amd64 
(390.48-0ubuntu3)
End-Date: 2018-05-17  11:35:01


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

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Currently, the Additional Drivers tool uninstalls only the driver package 
that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that 
package is only a meta-package. Removing the meta-package will not uninstall 
the driver.

  We should make sure to uninstall all its nvidia related dependencies,
  not only the meta-package.

  [Test Case]
  1) Open the "Software & Updates" app, and select the "Additional Drivers" tab

  2) Uninstall the NVIDIA 390 driver

  3) Check that, for example, the nvidia-dkms-390 package was
  uninstalled:

  apt-cache policy nvidia-dkms-390

  The package will be reported as installed, because the current code
  didn't remove it.

  [Regression Potential]
  Relatively low, as the change in behaviour only affects the nvidia driver, 
and it only causes the Additional Drivers tool to remove dependencies of the 
meta-package that have the "nvidia" string in their name.

  __
  When you are in the initial install state, you can easily switch from the 
Nouvea drivers to the Nvidia drivers by choosing the option in "Software and 
Updates -> Additional Drivers".  However, when you attempt to switch back (by 
selecting the nouveau option and clicking Apply), and subsequently reboot, your 
system will still come up using the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

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

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

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

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

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

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

[Jorge Gustavo]

Hello César Bento Freire,

I've wrote a small tutorial about installing Portuguese Citizen Smartcard 
Software, at 
https://blog.geomaster.pt/cartao-de-cidadao-no-ubuntu-18-04/

You can install manually libxerces-c3.1 as Evgeny Brazgin explained.

It also depends on libcurl3. To install Evgeny Brazgin packages, please
do:

sudo add-apt-repository ppa:xapienz/curl34
sudo apt policy curl
sudo apt remove curl libcurl4
sudo apt install curl=7.58.0-2ubuntu3ppa2 libcurl4=7.58.0-2ubuntu3ppa2

Evgeny Brazgin: thank you for providing the packages! Well done!

-- 
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 1771870] [NEW] [USB-Audio - Logitech G933 Gaming Wireless H, playback] volume controls wrong output

[CuTeBoi]

Public bug reported:

I have multiple outputs:

I have a Dell AC511 USB Soundbar which has its own volume control
I have a G15 Logitech Keyboard with volume control
I have a G933 Wireless USB Gaming headset with a volume control


Currently I have my default output for the whole system is the Dell AC511 USB 
Soundbar.
Chrome has configured communication device as the G933 headset, NOT the 
"Default" sound.


I am unable to control the volume independently of the headset or the system 
with the correct volume controls.


I change volume on my G933 Headset, and the volume of the system is being 
controlled, and the volume does not change on the headset.

I change the volume of the G15 and the Dell AC511, and they correctly
control the system volume.


This was not an issue on 16.04, each volume control would control its output 
correctly, while the G15 always controlled the System Volume, never the headset.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 17 13:09:51 2018
InstallationDate: Installed on 2018-05-16 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: G933 Wireless Headset Dongle - Logitech G933 Gaming Wireless H
Symptom_PulseAudioLog:
 
Symptom_Type: Volume slider, or mixer problems
Title: [USB-Audio - Logitech G933 Gaming Wireless H, playback] volume slider 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1402
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

Title:
  [USB-Audio - Logitech G933 Gaming Wireless H, playback] volume
  controls wrong output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have multiple outputs:

  I have a Dell AC511 USB Soundbar which has its own volume control
  I have a G15 Logitech Keyboard with volume control
  I have a G933 Wireless USB Gaming headset with a volume control

  
  Currently I have my default output for the whole system is the Dell AC511 USB 
Soundbar.
  Chrome has configured communication device as the G933 headset, NOT the 
"Default" sound.

  
  I am unable to control the volume independently of the headset or the system 
with the correct volume controls.

  
  I change volume on my G933 Headset, and the volume of the system is being 
controlled, and the volume does not change on the headset.

  I change the volume of the G15 and the Dell AC511, and they correctly
  control the system volume.

  
  This was not an issue on 16.04, each volume control would control its output 
correctly, while the G15 always controlled the System Volume, never the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 17 13:09:51 2018
  InstallationDate: Installed on 2018-05-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: G933 Wireless Headset Dongle - Logitech G933 Gaming Wireless H
  Symptom_PulseAudioLog:
   
  Symptom_Type: Volume slider, or mixer problems
  Title: [USB-Audio - Logitech G933 Gaming Wireless H, playback] volume slider 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: 

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

[Brian Murray]

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1771858] [NEW] /snap/bin not in default PATH for units

[Dan Watkins]

Public bug reported:

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

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

Title:
  /snap/bin not in default PATH for units

Status in systemd package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1767875] Re: /usr/bin/update-manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate

[Launchpad Bug Tracker]

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

** Changed in: update-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  /usr/bin/update-
  
manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate

Status in apt package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-manager.  This problem was most recently seen with package version 
1:18.04.11, the problem page at 
https://errors.ubuntu.com/problem/a2ba8d3ab5e432b3c15f172ded6d473f4c00720a 
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/apt/+bug/1767875/+subscriptions

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

[Touch-packages] [Bug 1770224] Re: unattended-upgrades crashes with: apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages

[Balint Reczey]

Resolver, just fixed the trace from the error.

** Description changed:

  It seems pkgProblemResolver is hitting an internal bug quite frequently
  with latest u-u:
  
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
-   File "/usr/bin/unattended-upgrade", line 1822, in main
- options.dry_run)
-   File "/usr/bin/unattended-upgrade", line 1399, in do_auto_remove
- res, error = cache_commit(cache, logfile_dpkg, verbose)
-   File "/usr/bin/unattended-upgrade", line 513, in cache_commit
- res = cache.commit(install_progress=iprogress)
-   File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in commit
- res = self._fetch_archives(fetcher, pm)
-   File "/usr/lib/python3/dist-packages/apt/cache.py", line 385, in 
_fetch_archives
- raise LockFailedException("Failed to lock %s" % lockfile)
- apt.cache.LockFailedException: Failed to lock /var/cache/apt/archives/lock
+   File "/usr/bin/unattended-upgrade", line 1678, in main
+ pkg.mark_upgrade(from_user=not pkg.is_auto_installed)
+   File "/usr/lib/python3/dist-packages/apt/package.py", line 1483, in 
mark_upgrade
+ self.mark_install(from_user=from_user)
+   File "/usr/lib/python3/dist-packages/apt/package.py", line 1475, in 
mark_install
+ fixer.resolve(True)
+ apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this 
may be caused by held packages.
  
- 
- I believe this should be fixed in apt rather than just catching it in u-u.
+ I believe this should be fixed in apt rather than just catching it in
+ u-u.
  
  More info:
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/49de8d44b4ceccb27b66921173ee7e837e7a1e54 
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/.

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

Title:
  unattended-upgrades crashes with: apt_pkg.Error: E:Error,
  pkgProblemResolver::Resolve generated breaks, this may be caused by
  held packages

Status in apt package in Ubuntu:
  New

Bug description:
  It seems pkgProblemResolver is hitting an internal bug quite
  frequently with latest u-u:

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1678, in main
  pkg.mark_upgrade(from_user=not pkg.is_auto_installed)
File "/usr/lib/python3/dist-packages/apt/package.py", line 1483, in 
mark_upgrade
  self.mark_install(from_user=from_user)
File "/usr/lib/python3/dist-packages/apt/package.py", line 1475, in 
mark_install
  fixer.resolve(True)
  apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this 
may be caused by held packages.

  I believe this should be fixed in apt rather than just catching it in
  u-u.

  More info:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/49de8d44b4ceccb27b66921173ee7e837e7a1e54 
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/apt/+bug/1770224/+subscriptions

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

[Touch-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts

[Andy Pieters]

ok scratch the part about the syntax error as I have fixed my PAC file.

which leaves...

you can encounter this problem if you have a proxy server configured.

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

Title:
  kde-telepathy, impossible to connect to gmail accounts

Status in meta-kde-telepathy package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  Im running ubuntu 12.10 quantal and i have installed kde, when running
  kde-telepathy i have added a gmail account, and after entering the
  password it has revealed impossible to connect to it, it always says
  that the password is wrong when that is false.

  When using empathy, i have removed the gmail account and have added it
  again, now appears a XMLL window asking ubuntu permission to conenct
  to it, and now i was able to conenct to the gmail account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions

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

[Touch-packages] [Bug 1771839] [NEW] keyboard

[Miguel Velasco Ortega]

Public bug reported:

The keyboard is desconfigurated for spanish.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu May 17 10:03:40 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:06fb]
InstallationDate: Installed on 2017-04-21 (390 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Dell Inc. Vostro 3250
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.5.2
dmi.board.name: 0J4NFV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: Vostro
dmi.product.name: Vostro 3250
dmi.product.version: X00
dmi.sys.vendor: Dell Inc.
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 N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu May 17 08:46:00 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputDP-1  HDMI-1
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  keyboard

Status in xorg package in Ubuntu:
  New

Bug description:
  The keyboard is desconfigurated for spanish.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu May 17 10:03:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06fb]
  InstallationDate: Installed on 2017-04-21 (390 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Vostro 3250
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.5.2
  dmi.board.name: 0J4NFV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3250
  dmi.product.version: X00
  dmi.sys.vendor: Dell Inc.
  version.compiz: 

[Touch-packages] [Bug 1752737] Re: [2.3.0-6434] mDNS observer problems

[Andres Rodriguez]

** Changed in: maas
Milestone: 2.4.0beta4 => 2.4.x

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

Title:
  [2.3.0-6434] mDNS observer problems

Status in Avahi:
  Unknown
Status in MAAS:
  Triaged
Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  I see avahi-browser choking on non-utf8 characters in my rackd.log:

  ==> rackd.log <==
  2018-02-28 16:54:33 provisioningserver.utils.services: [info] mDNS 
observation process started.
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
Traceback (most recent call last):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 87, in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 83, in main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
run()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 52, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
from provisioningserver.__main__ import main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/__main__.py", line 55, 
in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
91, in __call__
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
self.execute(argv)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
86, in execute
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
args.handler.run(args)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
221, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
_observe_mdns(reader, output, args.verbose)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
145, in _observe_mdns
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in observer(events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
161, in _observe_resolver_found
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in filter(_p_resolver_found, events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
125, in _extract_mdns_events
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in map(parse_avahi_event, lines):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
(result, consumed) = self._buffer_decode(data, self.errors, final)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc8 in position 240: 
invalid continuation byte
  2018-02-28 16:54:36 provisioningserver.utils.services: [critical] mDNS 
observation process failed.

  Traceback (most recent call last):
  Failure: twisted.internet.error.ProcessTerminated: A process has ended with a 
probable error condition: process ended with exit code 1.

  ==> regiond.log <==
  2018-02-28 16:54:50 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
  2018-02-28 16:55:20 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

  ==> maas.log <==
  Feb 28 16:53:52 MAAS-RC01 maas.interface: [info] ens33 (physical) on 
MAAS-RC01: New MAC, IP binding observed: 08:eb:74:ca:d3:6f, 192.168.1.82

  Similar traceback when running from command line:

  maasuser@MAAS-RC01:~$ maas-rack observe-mdns
  {"hostname": "Apple-TV", "interface": "ens33", "address": "192.168.1.81"}
  Got SIGTERM, quitting.
  Traceback (most recent call last):
File "/usr/sbin/maas-rack", line 87, in 
  main()
File "/usr/sbin/maas-rack", line 83, in main
  run()

[Touch-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts

[Andy Pieters]

I have discovered the cause for this.

You are using a proxy with an autoconfiguration URL (PAC script) which
has got a syntax error in it (as far as WebKit is concerned)

When you run the add account it calls signon-ui and it segfaults because
of this.

If you use konqueror you may also experience problems. In my case, it
takes a very long time to load pages, like almost a minute long.

If you can, temporarily disable your proxy, or if you cannot connect
without proxy, try manually setting the address of the proxy (not the
PAC stript), for the duration of adding the account.

Once the account has been added, signon-ui isn't needed, and the proxy
settings can be re-instated.


** Attachment added: "backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+attachment/5140871/+files/bt

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

Title:
  kde-telepathy, impossible to connect to gmail accounts

Status in meta-kde-telepathy package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  Im running ubuntu 12.10 quantal and i have installed kde, when running
  kde-telepathy i have added a gmail account, and after entering the
  password it has revealed impossible to connect to it, it always says
  that the password is wrong when that is false.

  When using empathy, i have removed the gmail account and have added it
  again, now appears a XMLL window asking ubuntu permission to conenct
  to it, and now i was able to conenct to the gmail account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions

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

[Touch-packages] [Bug 1698593] Re: [Blade, Realtek ALC298, Black Mic, Left] No sound at all

[Daniel Martin]

Use the following parameter...

options snd-hda-intel model=laptop-dmic

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

Title:
  [Blade, Realtek ALC298, Black Mic, Left] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to get the mic from the combo jack on my Razer Blade
  working. Headphones are functioning perfectly, but the mic seems to be
  picking up on random data, unrelated to sound output or my
  surroundings. I know the jack is working as I dual-boot Windows, and
  it works great there.

  I've added the `options snd-hda-intel model=laptop-dmic` line as
  recommended in some other threads, and tried setting pin 0x18 to mic
  using hdajackretask, but it hasn't fixed it or made any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
   /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
   /dev/snd/controlC0:  octy   1971 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Sat Jun 17 15:21:41 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-06 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
   /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
   /dev/snd/controlC0:  octy   1971 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (63 days ago)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:06:35.753276

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

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

[Touch-packages] [Bug 1769891] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)

[Antoine]

** Changed in: deja-dup
   Status: New => Confirmed

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

Title:
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
  37: ordinal not in range(128)

Status in Déjà Dup:
  Confirmed
Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Hello

  duplicity crash after backup because there is a python error

  Step to reproduce.

  1. Active developper option in software center
  2. install the backup python pyckage
  3. Lanch a backup with duplicity command

  Result :

  
   Type of backup set:Time:   Number of volumes:
  Full Tue Feb 20 22:00:34 2018  2284
   Incremental Thu Feb 22 03:26:48 2018 1
   Incremental Fri Feb 23 23:23:09 201842
   Incremental Wed Apr  4 15:54:05 2018   151
   Incremental Thu Apr  5 04:27:55 2018 1
   Incremental Sat Apr 14 21:51:41 2018 1
  -
  Also found 0 backup sets not part of any chain,
  and 1 incomplete backup set.
  These may be deleted by running duplicity with the "cleanup" command.
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Deleting /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Forgetting temporary file /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Processing remote manifest 
duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest (154)
  Found manifest volume 1
  Found 1 volumes in manifest
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 556, in 
get
  "from backend") % util.ufn(local_path.name))
   BackendException: File /tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not 
found locally after get from backend

  Attempt 1 failed. BackendException: File 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found locally after get from 
backend
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 552, in 
get
  self.backend._get(remote_filename, local_path)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 151, in _get
  self.__copy_file(source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 124, in __copy_file
  None, self.__copy_progress, None)
   Error: g-io-error-quark: Error opening file 
“/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3”: No such file or directory 
(1)

  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mkstemp-useaK1-1
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Cleanup of temporary directory /tmp/duplicity-hFkoYG-tempdir failed - this is 
probably a bug.
  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 658, in incremental_backup
  sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 539, 
in get_fileobjs
  return [filename_to_fileobj(f) for f in self.get_filenames(time)]
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 676, in 
get_fileobj_read
  self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in 
inner_retry
  util.uexc(e)), code=code, extra=extra)
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  Releasing lockfile /home/username/.cache/deja-
  dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile

  Note : this bug affect eclim and other python pyckages

  http://eclim.org

  
  Could you help me please to fix this issus

  Best regards

  Battant

  ProblemType: Bug
  DistroRelease: 

[Touch-packages] [Bug 1769891] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)

[Launchpad Bug Tracker]

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

** Changed in: python2.7 (Ubuntu)
   Status: New => Confirmed

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

Title:
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
  37: ordinal not in range(128)

Status in Déjà Dup:
  Confirmed
Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Hello

  duplicity crash after backup because there is a python error

  Step to reproduce.

  1. Active developper option in software center
  2. install the backup python pyckage
  3. Lanch a backup with duplicity command

  Result :

  
   Type of backup set:Time:   Number of volumes:
  Full Tue Feb 20 22:00:34 2018  2284
   Incremental Thu Feb 22 03:26:48 2018 1
   Incremental Fri Feb 23 23:23:09 201842
   Incremental Wed Apr  4 15:54:05 2018   151
   Incremental Thu Apr  5 04:27:55 2018 1
   Incremental Sat Apr 14 21:51:41 2018 1
  -
  Also found 0 backup sets not part of any chain,
  and 1 incomplete backup set.
  These may be deleted by running duplicity with the "cleanup" command.
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Deleting /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Forgetting temporary file /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Processing remote manifest 
duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest (154)
  Found manifest volume 1
  Found 1 volumes in manifest
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 556, in 
get
  "from backend") % util.ufn(local_path.name))
   BackendException: File /tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not 
found locally after get from backend

  Attempt 1 failed. BackendException: File 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found locally after get from 
backend
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 552, in 
get
  self.backend._get(remote_filename, local_path)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 151, in _get
  self.__copy_file(source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 124, in __copy_file
  None, self.__copy_progress, None)
   Error: g-io-error-quark: Error opening file 
“/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3”: No such file or directory 
(1)

  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mkstemp-useaK1-1
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Cleanup of temporary directory /tmp/duplicity-hFkoYG-tempdir failed - this is 
probably a bug.
  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 658, in incremental_backup
  sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 539, 
in get_fileobjs
  return [filename_to_fileobj(f) for f in self.get_filenames(time)]
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 676, in 
get_fileobj_read
  self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in 
inner_retry
  util.uexc(e)), code=code, extra=extra)
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  Releasing lockfile /home/username/.cache/deja-
  dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile

  Note : this bug affect eclim and other python pyckages

  http://eclim.org

  
  Could you help me please 

[Touch-packages] [Bug 1771802] Re: enable rc-local.service unit by default

[Dimitri John Ledkov]

rc.local is enabled, and part of the initial boot target... if it
exists, and is executable.

Can you please provide steps, or details of your system, on which you
observe that it was not executed on boot? when present, and executable?

Note by default on ubuntu, there is no rc.local shipped. But would be
used, if there is one on boot.

# cat /etc/rc.local 
#!/bin/sh
echo Hello rc.local
exit 0

# sudo chmod +x /etc/rc.local
# sudo reboot
# journalctl -b -u rc-local.service
-- Logs begin at Thu 2018-05-17 13:22:46 UTC, end at Thu 2018-05-17 13:24:28 
UTC. --
May 17 13:23:39 test-rclocal systemd[1]: Starting /etc/rc.local Compatibility...
May 17 13:23:39 test-rclocal rc.local[205]: Hello rc.local
May 17 13:23:39 test-rclocal systemd[1]: Started /etc/rc.local Compatibility.


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

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

Title:
  enable rc-local.service unit by default

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Every other systemd-infected distribution leaves the rc-local.service
  unit enabled; this is probably because provisioning systems need to
  use it to launch first-boot tasks.

  Ubuntu has been blindly following suit in every other respect and
  should do the same here also.  It's a null op unless the file exists
  and is executable, so enabling it gives all the benefits for extremely
  negligible cost.

  Example reproducable bug:
  * preseed a new host and an rc.local expected to run on boot
  * boot and realise rc.local didn't run
  * realise you can't enable it in the preseed as systemctl is not affecting 
the target system
  * curse Lennart (again) and run Devuan instead where things just work as they 
should

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

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

[Touch-packages] [Bug 1771749] WifiSyslog.txt

[Victor Marin]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140838/+files/WifiSyslog.txt

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 

[Touch-packages] [Bug 1771749] ProcInterrupts.txt

[Victor Marin]

apport information

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

Re: [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

[Andrea Azzarone]

Yes. The other part is not required in 3.28.

Il gio 17 mag 2018, 03:31 Sebastien Bacher  ha
scritto:

> @andyrock, is https://gitlab.gnome.org/GNOME/gnome-control-
> center/merge_requests/49/diffs the correct fix for that segfault? it
> seems only half of the change from master, is that enough?
>
> --
> You received this bug notification because you are a bug assignee.
> 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:
>   In Progress
> Status in gtk+3.0 package in Ubuntu:
>   Fix Released
>
> Bug description:
>   * Impact
>   gnome-control-center sometimes hits a segfault
>
>   * Test case
>   - Check if the e.u.c reports stop with the new version
>
>   or
>
>   - Open GNOME Control Center
>   - Go to Devices->Display panel
>   - Close the window
>   - Open GNOME Control Center again (in overview mode)
>
>   the settings should open without error
>
>   * Regression potential
>   check the panels can be opened without error and that switching between
> them works as well
>
>   --
>
>   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
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center;
> component=main; status=In Progress; importance=High; assignee=
> andrea.azzar...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gtk+3.0; component=main;
> status=Fix Released; importance=High; assignee=
> andrea.azzar...@canonical.com;
> Launchpad-Bug-Tags: artful bionic patch
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: azzar1 crichton janitor jbicha seb128
> whoopsie-daisy-bug-bridge
> Launchpad-Bug-Reporter: errors.ubuntu.com bug bridge
> (whoopsie-daisy-bug-bridge)
> Launchpad-Bug-Modifier: Sebastien Bacher (seb128)
> Launchpad-Message-Rationale: Assignee
> Launchpad-Message-For: azzar1
>

-- 
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:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  gnome-control-center sometimes hits a segfault

  * Test case
  - Check if the e.u.c reports stop with the new version

  or

  - Open GNOME Control Center
  - Go to Devices->Display panel
  - Close the window
  - Open GNOME Control Center again (in overview mode) 

  the settings should open without error

  * Regression potential
  check the panels can be opened without error and that switching between them 
works as well

  --

  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 1771749] PulseList.txt

[Victor Marin]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140836/+files/PulseList.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
 

[Touch-packages] [Bug 1771749] ProcModules.txt

[Victor Marin]

apport information

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Touch-packages] [Bug 1771749] UdevDb.txt

[Victor Marin]

apport information

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  

[Touch-packages] [Bug 1771749] ProcCpuinfoMinimal.txt

[Victor Marin]

apport information

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Touch-packages] [Bug 1771749] ProcEnviron.txt

[Victor Marin]

apport information

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Touch-packages] [Bug 1771749] CurrentDmesg.txt

[Victor Marin]

apport information

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Touch-packages] [Bug 1771749] NetDevice.enp0s7.txt

[Victor Marin]

apport information

** Attachment added: "NetDevice.enp0s7.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140829/+files/NetDevice.enp0s7.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Touch-packages] [Bug 1771749] Lspci.txt

[Victor Marin]

apport information

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  

[Touch-packages] [Bug 1771749] NetworkManager.conf.txt

[Victor Marin]

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140831/+files/NetworkManager.conf.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Touch-packages] [Bug 1771749] Dependencies.txt

[Victor Marin]

apport information

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Touch-packages] [Bug 1771749] NetDevice.lo.txt

[Victor Marin]

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140830/+files/NetDevice.lo.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Touch-packages] [Bug 1771749] CRDA.txt

[Victor Marin]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1771749/+attachment/5140824/+files/CRDA.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  

[Touch-packages] [Bug 1771749] IpAddr.txt

[Victor Marin]

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1771749/+attachment/5140827/+files/IpAddr.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  

[Touch-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting

[Victor Marin]

apport information

** Tags added: apport-collected

** Description changed:

  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.
  
  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is
  most everything Ok, but -I think that- the network-manager has a
  problem.
  
  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or hours,
  but several times per day.
  
  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.
  
  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.
  
  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the scanner:
  If I plug it in some USB port of the laptop once Kubuntu 18.04 is
  already running, it's not detected by Xsane. I have to plug it in before
  than pressing the power button or at the time of starting the OS, for
  the scanner to be detected by the scanning program (and then only works
  with Xsane, not if I use Simple Scan or Skanlite, even when it works
  under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the
  scanner cable from the USB port it is not detected anymore when plugging
  it again, and only restarting the laptop makes it to be detected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  nosotros   1116 F pulseaudio
+  /dev/snd/controlC1:  nosotros   1116 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ InstallationDate: Installed on 2018-05-11 (6 days ago)
+ InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
+ IpRoute:
+  default via 192.168.1.1 dev enp0s7 proto static metric 100 
+  169.254.0.0/16 dev enp0s7 scope link metric 1000 
+  192.168.1.0/24 dev enp0s7 proto kernel scope 

[Touch-packages] [Bug 1771486] Re: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create()

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-logind crashed with SIGABRT in __libc_connect() from
  __GI_clnttcp_create() from __GI___libc_rpc_getport() from
  __GI_pmap_getport() from __GI_clnttcp_create()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 
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/systemd/+bug/1771486/+subscriptions

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

[Touch-packages] [Bug 1771485] Re: systemd-logind crashed with SIGABRT in log_assert_failed_realm() from close_nointr() from session_device_free() from session_release_controller() from session_drop_c

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-logind crashed with SIGABRT in log_assert_failed_realm() from
  close_nointr() from session_device_free() from
  session_release_controller() from session_drop_controller()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/c0d063b28aafc2663824a7f8f5b86fa757b0c467 
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/systemd/+bug/1771485/+subscriptions

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

[Touch-packages] [Bug 1770265] Re: package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Python install corrupted.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  9 14:01:46 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-10-26 (194 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[mrvanes]

Fixed for me using the above mentioned PPA.
Thx!

And I agree with Guillaume that, for me, this was a major annoyance
nonetheless...

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1771345] Re: lscpu possible crash in min/max frequency

[Julian Andres Klode]

xenial: 3.4 prints (null), 3.5 crashed, and 3.6 fixed it -> verified
artful: 4.1 in release crashes; 4.2 fixes it -> verified
bionic: 3 in release crashes, 3.1 fixes it -> verified

Sample log from bionic belog:


jak@jak-t480s:~/Downloads$ echo lscpu -s /home/jak/Downloads/segvtest | lxc 
exec b -- bash - 
bash: line 1:   285 Segmentation fault  (core dumped) lscpu -s 
/home/jak/Downloads/segvtest
- 
jak@jak-t480s:~/Downloads$ lxc exec b -- sh -c "echo 'deb 
http://archive.ubuntu.com/ubuntu bionic-proposed main' > /etc/apt/sources.list"
jak@jak-t480s:~/Downloads$ lxc exec b apt update
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease [242 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 
[35.9 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main Translation-en 
[14.7 kB]
Fetched 293 kB in 1s (472 kB/s)   
Reading package lists... Done
Building dependency tree   
Reading state information... Done
17 packages can be upgraded. Run 'apt list --upgradable' to see them.
jak@jak-t480s:~/Downloads$ lxc exec b apt install -q util-linux
Error: unknown shorthand flag: 'q' in -q
jak@jak-t480s:~/Downloads$ lxc exec b -- apt install -q util-linux
Reading package lists...
Building dependency tree...
Reading state information...
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
Suggested packages:
  util-linux-locales
The following packages will be upgraded:
  util-linux
1 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.
Need to get 902 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 util-linux 
amd64 2.31.1-0.4ubuntu3.1 [902 kB]
Fetched 902 kB in 1s (990 kB/s)
(Reading database ... 28477 files and directories currently installed.)
Preparing to unpack .../util-linux_2.31.1-0.4ubuntu3.1_amd64.deb ...
Unpacking util-linux (2.31.1-0.4ubuntu3.1) over (2.31.1-0.4ubuntu3) ...
Setting up util-linux (2.31.1-0.4ubuntu3.1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.3-2) ...
jak@jak-t480s:~/Downloads$ echo lscpu -s /home/jak/Downloads/segvtest | lxc 
exec b -- bash - 
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
CPU(s):  8
On-line CPU(s) list: 0-7
Thread(s) per core:  2
Core(s) per socket:  4
Socket(s):   1
NUMA node(s):1
Vendor ID:   GenuineIntel
CPU family:  6
Model:   142
Model name:  Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Stepping:10
CPU max MHz: 3400.
CPU min MHz: 400.
BogoMIPS:3600.00
Virtualization:  VT-x
L1d cache:   32K
L1i cache:   32K
L2 cache:256K
L3 cache:6144K
NUMA node0 CPU(s):   0-7
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 
x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 
3dnowprefetch cpuid_fault epb invpcid_single pti tpr_shadow vnmi flexpriority 
ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx 
smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves ibpb ibrs stibp dtherm 
ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp


** Tags added: verification-done-artful verification-done-bionic 
verification-done-xenial

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

Title:
  lscpu possible crash in min/max frequency

Status in util-linux package in Ubuntu:
  Fix Committed
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:

  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd

  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2

  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).

  [Regression 

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Julian Andres Klode]

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

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Julian Andres Klode]

ppaid...@in.ibm.com Can you check with the new util-linux in proposed
(2.27.1-6ubuntu3.6)? This should fix the crash.

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   

[Touch-packages] [Bug 1771802] [NEW] enable rc-local.service unit by default

[Matthew Hawkins]

Public bug reported:

Every other systemd-infected distribution leaves the rc-local.service
unit enabled; this is probably because provisioning systems need to use
it to launch first-boot tasks.

Ubuntu has been blindly following suit in every other respect and should
do the same here also.  It's a null op unless the file exists and is
executable, so enabling it gives all the benefits for extremely
negligible cost.

Example reproducable bug:
* preseed a new host and an rc.local expected to run on boot
* boot and realise rc.local didn't run
* realise you can't enable it in the preseed as systemctl is not affecting the 
target system
* curse Lennart (again) and run Devuan instead where things just work as they 
should

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

Title:
  enable rc-local.service unit by default

Status in systemd package in Ubuntu:
  New

Bug description:
  Every other systemd-infected distribution leaves the rc-local.service
  unit enabled; this is probably because provisioning systems need to
  use it to launch first-boot tasks.

  Ubuntu has been blindly following suit in every other respect and
  should do the same here also.  It's a null op unless the file exists
  and is executable, so enabling it gives all the benefits for extremely
  negligible cost.

  Example reproducable bug:
  * preseed a new host and an rc.local expected to run on boot
  * boot and realise rc.local didn't run
  * realise you can't enable it in the preseed as systemctl is not affecting 
the target system
  * curse Lennart (again) and run Devuan instead where things just work as they 
should

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

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

[Touch-packages] [Bug 1771791] Re: Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Unknown => 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/1771791

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  New

Bug description:
  [Impact]
  systemd used to pre-depend on the libraries used by systemctl or something, 
but now systemctl uses libsystemd-shared, and there are no pre-depends for 
that, meaning that systemctl fails in maintainer scripts of other packages.

  [Test case]
  Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

  [Regression potential]
  Installation ordering changes. Might make things harder for apt to solve.

  [Other info]
  Debian 897986

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

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

[Touch-packages] [Bug 1771791] [NEW] Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

[Julian Andres Klode]

Public bug reported:

[Impact]
systemd used to pre-depend on the libraries used by systemctl or something, but 
now systemctl uses libsystemd-shared, and there are no pre-depends for that, 
meaning that systemctl fails in maintainer scripts of other packages.

[Test case]
Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

[Regression potential]
Installation ordering changes. Might make things harder for apt to solve.

[Other info]
Debian 897986

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

** Affects: systemd (Debian)
 Importance: Unknown
 Status: Unknown

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

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

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

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

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

Bug description:
  [Impact]
  systemd used to pre-depend on the libraries used by systemctl or something, 
but now systemctl uses libsystemd-shared, and there are no pre-depends for 
that, meaning that systemctl fails in maintainer scripts of other packages.

  [Test case]
  Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

  [Regression potential]
  Installation ordering changes. Might make things harder for apt to solve.

  [Other info]
  Debian 897986

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

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

[Touch-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial

[Nicolas Dichtel]

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

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

Title:
  iproute2: unable to add ip lwt mpls route on xenial

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  The following command does not work:

  $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
  Error: "nexthop" or end of line is expected instead of "encap"

  In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
  $ ip -V
  ip utility, iproute2-ss151103

  =>
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4

  With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
  $ modprobe mpls_iptunnel
  $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev 
ntfp2
  $ ./ip/ip r
  [snip]
  10.201.0.0/24  encap mpls  300 via 10.200.0.1 dev ntfp2

  At least, this patch is missing:
  1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02

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

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

[Touch-packages] [Bug 1771783] [NEW] iproute2: frr route protocols are not converted to string on xenial

[Nicolas Dichtel]

Public bug reported:

FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

A patch has been pushed upstream so that external applications can define their 
protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

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

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

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

[Touch-packages] [Bug 1771764] [NEW] iproute2: unable to add ip lwt mpls route on xenial

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The following command does not work:

$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"

In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103

=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4

With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev 
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24  encap mpls  300 via 10.200.0.1 dev ntfp2

At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: xenial
-- 
iproute2: unable to add ip lwt mpls route on xenial
https://bugs.launchpad.net/bugs/1771764
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to iproute2 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 1771783] [NEW] iproute2: frr route protocols are not converted to string on xenial

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

A patch has been pushed upstream so that external applications can define their 
protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

-- 
iproute2: frr route protocols are not converted to string on xenial
https://bugs.launchpad.net/bugs/1771783
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to iproute2 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 1771359] Re: No matching cipher found even if client and server have matching cipher

[Joseph Maillardet]

It's not a bug !

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/openssh/+question/669164

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

Title:
  No matching cipher found even if client and server have matching
  cipher

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Since Bionic upgrade (from Artful) I encounter problem to call HP
  switch with SSH.

  After the upgrade, trying to ssh some switch give me this message :

  $ ssh 192.168.0.1
  Unable to negotiate with 192.168.0.1 port 22: no matching cipher found. Their 
offer: aes128-cbc,3des-cbc,des-cbc

  So, I look for supported cipher :

  $ ssh -Q cipher
  3des-cbc
  aes128-cbc
  aes192-cbc
  aes256-cbc
  rijndael-...@lysator.liu.se
  aes128-ctr
  aes192-ctr
  aes256-ctr
  aes128-...@openssh.com
  aes256-...@openssh.com
  chacha20-poly1...@openssh.com

  I see that aes128-cbc seem both supported. So I try... :

  $ ssh -c aes128-cbc 192.168.0.1

  ...and It's work !

  Workaround :

  I've added “ciphers aes128-cbc” to ~/.ssh/config file for each switch
  I manage.

  The ssh-client should detect automatically the good cipher ? No ?

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 15 15:39:00 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:7.6p1-4
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (21 days ago)

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

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

[Touch-packages] [Bug 1771359] Re: No matching cipher found even if client and server have matching cipher

[Joseph Maillardet]

Thank you for your reply.
I'm sorry, I did not think about watching the ChangeLog. Indeed, it is not a 
bug, it may be closed.

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

Title:
  No matching cipher found even if client and server have matching
  cipher

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Since Bionic upgrade (from Artful) I encounter problem to call HP
  switch with SSH.

  After the upgrade, trying to ssh some switch give me this message :

  $ ssh 192.168.0.1
  Unable to negotiate with 192.168.0.1 port 22: no matching cipher found. Their 
offer: aes128-cbc,3des-cbc,des-cbc

  So, I look for supported cipher :

  $ ssh -Q cipher
  3des-cbc
  aes128-cbc
  aes192-cbc
  aes256-cbc
  rijndael-...@lysator.liu.se
  aes128-ctr
  aes192-ctr
  aes256-ctr
  aes128-...@openssh.com
  aes256-...@openssh.com
  chacha20-poly1...@openssh.com

  I see that aes128-cbc seem both supported. So I try... :

  $ ssh -c aes128-cbc 192.168.0.1

  ...and It's work !

  Workaround :

  I've added “ciphers aes128-cbc” to ~/.ssh/config file for each switch
  I manage.

  The ssh-client should detect automatically the good cipher ? No ?

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 15 15:39:00 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:7.6p1-4
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (21 days ago)

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

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

[Touch-packages] [Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04

[Dimitri John Ledkov]

Please provide the contents of /etc/netplan on the affected systems, and
please let me know, if removing files in said directory makes networkd
ignore interfaces.

Please provide output of $ networkctl

By default, if there is no netplan configuration, networkd does not
"force use of systemd-networkd" and "does not interferes with ifupdown".
Thus specifics about your system are required to describe the bug in
detail and/or eventually fix Ubuntu or specific systems in question.

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

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

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

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

Title:
  forced use of systemd-networkd interferes with ifupdown in 18.04

Status in ifupdown package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For several reasons, we are not able to use netplan nor systemd-
  networkd due to legacy applications that expect ifupdown's pre-up and
  post-up script mechanism.  The documentation around 18.04's
  (premature, I feel) wholesale adoption of netplan claims that one can
  revert to old behaviour by merely installing ifupdown (amongst
  assertions that netplan will never offer a mechanism for configuring
  pre-up and post-up actions even for network managers that support
  them).

  However when ifupdown is installed, systemd-networkd still tries to
  manage interfaces.  If you 'systemctl disable systemd-networkd', upon
  next reboot it is automatically re-enabled.  We tried disabling any
  systemd units even remotely related to networking and yet systemd-
  networkd still runs.  If it hasn't been configured, it tries to DHCP.
  On networks that don't provide DHCP this results in a stupendously
  long stall during boot.  Currently it appears to be impossible to tell
  systemd-networkd not to run in a clean manner that won't get reverted
  on package upgrades.

  I sincerely hope this is is a bug/oversight and not intentional.  We
  need to be able to disable systemd-networkd properly.

  Thanks

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

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

[Touch-packages] [Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04

[Dimitri John Ledkov]

@wes234234

A simple "apt install ifupdown" will not undo everything that installer
has done to setup the system, nor redo it for the alternative networking
management tool. Where do you expect ifupdown configs to materialize
from? And how do you expect the netplan configs be removed? Given that
the system is sensitive to all configs present on disk. This is similar
situation to how on the desktop one cannot simply "remove network-
manager & install ifupdown" to switch to ifupdown.

"there are plenty of examples" -> can you please give the examples that
you have experienced, specifically? the ubuntu developers have gone
extensive amount of porting, and integration testing to ensure that as
many things as possible are fixed to work, both on new installs and
upgrades.

I really want to know what is still broken and still needs fixing.

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

Title:
  forced use of systemd-networkd interferes with ifupdown in 18.04

Status in ifupdown package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For several reasons, we are not able to use netplan nor systemd-
  networkd due to legacy applications that expect ifupdown's pre-up and
  post-up script mechanism.  The documentation around 18.04's
  (premature, I feel) wholesale adoption of netplan claims that one can
  revert to old behaviour by merely installing ifupdown (amongst
  assertions that netplan will never offer a mechanism for configuring
  pre-up and post-up actions even for network managers that support
  them).

  However when ifupdown is installed, systemd-networkd still tries to
  manage interfaces.  If you 'systemctl disable systemd-networkd', upon
  next reboot it is automatically re-enabled.  We tried disabling any
  systemd units even remotely related to networking and yet systemd-
  networkd still runs.  If it hasn't been configured, it tries to DHCP.
  On networks that don't provide DHCP this results in a stupendously
  long stall during boot.  Currently it appears to be impossible to tell
  systemd-networkd not to run in a clean manner that won't get reverted
  on package upgrades.

  I sincerely hope this is is a bug/oversight and not intentional.  We
  need to be able to disable systemd-networkd properly.

  Thanks

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Sebastien Bacher]

@andyrock, is https://gitlab.gnome.org/GNOME/gnome-control-
center/merge_requests/49/diffs the correct fix for that segfault? it
seems only half of the change from master, is that enough?

-- 
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:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  gnome-control-center sometimes hits a segfault

  * Test case
  - Check if the e.u.c reports stop with the new version

  or

  - Open GNOME Control Center
  - Go to Devices->Display panel
  - Close the window
  - Open GNOME Control Center again (in overview mode) 

  the settings should open without error

  * Regression potential
  check the panels can be opened without error and that switching between them 
works as well

  --

  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 1771749] Re: Ethernet connection lost after few minutes since starting

[Kai-Heng Feng]

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1771749] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1771749

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  

[Touch-packages] [Bug 1771757] [NEW] Ubuntu doesn't detect device on USB 3.1 Gen 2 port

[Hairong Zhu]

Public bug reported:

Ubuntu does't detect the device when I plug a USB Flash drive onto the USB 3.1 
Gen 2 port on my motherboard. I can't find the device in lsusb output. If I 
reboot the system with the drive plugged, I can mount the drive in file 
manager. If I unplug and plug it again, Ubuntu doesn't detect the device.
My motherboard is ASUS ROG STRIX B360-G. Tried stock bionic and latest 
v4.16/v4.17 mainline kernels.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
Uname: Linux 4.16.9-041609-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu May 17 15:19:47 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: kubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
 virtualbox, 5.2.10, 4.16.9-041609-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
InstallationDate: Installed on 2018-03-03 (74 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180303)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.9-041609-generic 
root=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 ro 
resume=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 resume_offset=34816
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0602
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX B360-G GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd03/23/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB360-GGAMING:rvrRev1.xx: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-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: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic kubuntu

** Package changed: xorg (Ubuntu) => 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/1771757

Title:
  Ubuntu doesn't detect device on USB 3.1 Gen 2 port

Status in Ubuntu:
  New

Bug description:
  Ubuntu does't detect the device when I plug a USB Flash drive onto the USB 
3.1 Gen 2 port on my motherboard. I can't find the device in lsusb output. If I 
reboot the system with the drive plugged, I can mount the drive in file 
manager. If I unplug and plug it again, Ubuntu doesn't detect the device.
  My motherboard is ASUS ROG STRIX B360-G. Tried stock bionic and latest 
v4.16/v4.17 mainline kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  Uname: Linux 4.16.9-041609-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu May 17 15:19:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.16.9-041609-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-03 (74 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180303)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.9-041609-generic 
root=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 ro 
resume=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 resume_offset=34816
  SourcePackage: 

[Touch-packages] [Bug 1751252] Update Released

[Łukasz Zemczak]

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from 

[Touch-packages] [Bug 1771749] [NEW] Ethernet connection lost after few minutes since starting

[Victor Marin]

Public bug reported:


This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is
most everything Ok, but -I think that- the network-manager has a
problem.

In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
remember well, I never lost connection through Ethernet (the only
Internet connection with our desktop PC), but the Bionic Beaver loses
the connection every now and then, perhaps within few minutes or hours,
but several times per day.

When the connection is lost, I note that it disappears any info even
mention to any network into the network window and the network manager
icon becomes red color.

Not matter if I unplug and then plug the ethernet cable again, the
ethernet connection is not longer detected and only restarting the PC
makes the connection to work again.

Incidentally, I also have noticed with this version of Kubuntu 18.04
that in my laptop there is also now a similar problem with the scanner:
If I plug it in some USB port of the laptop once Kubuntu 18.04 is
already running, it's not detected by Xsane. I have to plug it in before
than pressing the power button or at the time of starting the OS, for
the scanner to be detected by the scanning program (and then only works
with Xsane, not if I use Simple Scan or Skanlite, even when it works
under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the
scanner cable from the USB port it is not detected anymore when plugging
it again, and only restarting the laptop makes it to be detected.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Thu May 17 08:24:23 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-05-11 (5 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.1.1 dev enp0s7 proto static metric 100 
 169.254.0.0/16 dev enp0s7 scope link metric 1000 
 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
IwConfig:
 enp0s7no wireless extensions.
 
 lono wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
PciNetwork:
 
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID  TYPE  TIMESTAMP 
  TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
 enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  Ethernet connection lost after few minutes since starting

Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection 

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 18.04.14.1

---
ubiquity (18.04.14.1) bionic; urgency=medium

  [ Iain Lane ]
  * Update Vcs-* for git migration

  [ Andrea Azzarone ]
  * misc.py: Restore the corrent euid in regain_privileges_save. Calling
regain_privileges_save should restore the effective user-id to the one
before the call  to drop_privileges_save. We need to call os.setresuid and
os.setresgid twice to avoid permission issues when calling os.setgroups.
(LP: #1751252)

 -- Iain Lane   Tue, 08 May 2018 15:22:49 +0100

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from 

[Touch-packages] [Bug 1770848] Re: Ethernet connection lost after few minutes since starting

[Victor Marin]

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

** This bug has been marked a duplicate of bug 1771749
   Ethernet connection lost after few minutes since starting

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

Title:
  Ethernet connection lost after few minutes since starting

Status in xorg package in Ubuntu:
  New

Bug description:
  I just upgraded from Kubuntu 16.04 to 18.04 and it is most everything
  Ok, but -I think that- the network-manager has a problem now.

  In the last LTS version I never lost connection through Ethernet (the
  only Internet connection with our desktop PC), but the Bionic Beaver
  loses the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  Only restarting the PC makes the connection to work again.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat May 12 15:37:10 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1458:2548]
  InstallationDate: Installed on 2018-05-11 (1 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 04fc:0005 Sunplus Technology Co., Ltd USB 
OpticalWheel Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d1d6ad93-b21c-43cd-8410-782414a5f935 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N68-S
  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.:bvrP1.50:bd07/17/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S: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

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

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

[Touch-packages] [Bug 1771747] [NEW] On left/right/Upside-down rotations, UI window getting sliced when trying to perform any operation

[Hao-Sheng Lu]

Public bug reported:

Steps to reproduce issue:

1) Connect the client with DP-DP
2) Login
3) Navigate to settings>Display
4) Select rotation as left (OR) right (OR) upside-down and apply
5) Try to perform any operation (Try to drag any UI window and observe the 
behavior )

Actual Results:
UI window getting sliced when trying to perform any operation.

Expected Results:
Should not get any distortion or slicing when trying to perform any operation.

Additional info:
Primary screen: Dell P2317H
Secondary screen: Viewsonic VX245MH

I can indeed see a kind of diagonal tearing when one of the screens is
rotated or inverted. See attached video showing how dragging a window
back and forth on the secondary screen shows this.

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

Title:
  On left/right/Upside-down rotations, UI window getting sliced when
  trying to perform any operation

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce issue:

  1) Connect the client with DP-DP
  2) Login
  3) Navigate to settings>Display
  4) Select rotation as left (OR) right (OR) upside-down and apply
  5) Try to perform any operation (Try to drag any UI window and observe the 
behavior )

  Actual Results:
  UI window getting sliced when trying to perform any operation.

  Expected Results:
  Should not get any distortion or slicing when trying to perform any operation.

  Additional info:
  Primary screen: Dell P2317H
  Secondary screen: Viewsonic VX245MH

  I can indeed see a kind of diagonal tearing when one of the screens is
  rotated or inverted. See attached video showing how dragging a window
  back and forth on the secondary screen shows this.

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

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