date:20200424

Can you tell me how to do that??


On Sat, 25 Apr 2020 at 03:11, Sebastien Bacher  wrote:

> Could you add the journal log?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874717
>
> Title:
>   devices cannot connect to ubuntu hotspot
>
> Status in network-manager package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
>   based internet connection to my ubuntu system via the hotspot
>   connection to my other devices.I am able to connect to my hospot
>   though. My ethernet connection works fine hotspot too but my devices
>   report:"This device has no connection to internet."Earlier in v18.04
>   it worked fine.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: ubuntu-release-upgrader-core 1:20.04.18
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CrashDB: ubuntu
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr 24 17:49:30 2020
>   InstallationDate: Installed on 2019-06-18 (310 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   PackageArchitecture: all
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_IN
>SHELL=/bin/bash
>   SourcePackage: ubuntu-release-upgrader
>   Symptom: dist-upgrade
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   VarLogDistupgradeTermlog:
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 20.04
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2019-06-18 (310 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   IpRoute:
>default via 10.20.2.1 dev enp2s0 proto static metric 100
>10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric
> 100
>10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric
> 600
>169.254.0.0/16 dev enp2s0 scope link metric 1000
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: network-manager 1.22.10-1ubuntu1
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Tags:  focal
>   Uname: Linux 5.4.0-26-generic x86_64
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.22.10  connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874717/+subscriptions
>

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

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback

[Touch-packages] [Bug 1874962] Re: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other

2020-04-24 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz',
  which is different from other instances of package
  libpango-1.0-0:amd64

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Rendering issues with the monospace default font (DejaVu Mono Book)
  led me to try and downgrade the libpango packages, which in turn
  caused this problem with the system packages.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpango-1.0-0 1.42.4-7~deb10u1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 23:15:13 2020
  DuplicateSignature:
   package:libpango-1.0-0:1.42.4-7~deb10u1
   Unpacking libpangocairo-1.0-0:amd64 (1.44.7-2ubuntu4) over 
(1.42.4-7~deb10u1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpangocairo-1.0-0_1.44.7-2ubuntu4_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/libpangocairo-1.0-0/copyright', 
which is different from other instances of package libpangocairo-1.0-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other 
instances of package libpango-1.0-0:amd64
  InstallationDate: Installed on 2014-09-11 (2052 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: pango1.0
  Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is 
different from other instances of package libpango-1.0-0:amd64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)

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

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

[Touch-packages] [Bug 1874962] [NEW] package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from othe

2020-04-24 Thread S7SoSt

Public bug reported:

Rendering issues with the monospace default font (DejaVu Mono Book) led
me to try and downgrade the libpango packages, which in turn caused this
problem with the system packages.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpango-1.0-0 1.42.4-7~deb10u1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 24 23:15:13 2020
DuplicateSignature:
 package:libpango-1.0-0:1.42.4-7~deb10u1
 Unpacking libpangocairo-1.0-0:amd64 (1.44.7-2ubuntu4) over (1.42.4-7~deb10u1) 
...
 dpkg: error processing archive 
/var/cache/apt/archives/libpangocairo-1.0-0_1.44.7-2ubuntu4_amd64.deb 
(--unpack):
  trying to overwrite shared '/usr/share/doc/libpangocairo-1.0-0/copyright', 
which is different from other instances of package libpangocairo-1.0-0:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other 
instances of package libpango-1.0-0:amd64
InstallationDate: Installed on 2014-09-11 (2052 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: pango1.0
Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is 
different from other instances of package libpango-1.0-0:amd64
UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)

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


** Tags: amd64 apport-package focal package-conflict

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

Title:
  package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz',
  which is different from other instances of package
  libpango-1.0-0:amd64

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Rendering issues with the monospace default font (DejaVu Mono Book)
  led me to try and downgrade the libpango packages, which in turn
  caused this problem with the system packages.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpango-1.0-0 1.42.4-7~deb10u1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 23:15:13 2020
  DuplicateSignature:
   package:libpango-1.0-0:1.42.4-7~deb10u1
   Unpacking libpangocairo-1.0-0:amd64 (1.44.7-2ubuntu4) over 
(1.42.4-7~deb10u1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpangocairo-1.0-0_1.44.7-2ubuntu4_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/libpangocairo-1.0-0/copyright', 
which is different from other instances of package libpangocairo-1.0-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other 
instances of package libpango-1.0-0:amd64
  InstallationDate: Installed on 2014-09-11 (2052 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: pango1.0
  Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is 
different from other instances of package libpango-1.0-0:amd64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)

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

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

[Touch-packages] [Bug 1867987] Re: Two possible sounds output, when playing movie from youtube, output is set to wrong one automatically after 5 seconds [, Realtek ALC283, Black Headphone Out, Left] f

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

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

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

Title:
  Two possible sounds output, when playing movie from youtube, output is
  set to wrong one automatically after 5 seconds [, Realtek ALC283,
  Black Headphone Out, Left] fails after a while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I start playing movie in Firefox and there is no sound coming out. I open 
sound configuration and change 
  "Output Device" from "HDMI / DispalyPort - Built in Audio" to "Headphones - 
Built in Audio"

  Sound starts to play and then after 5 seconds it stops again.

  When I open sound configuration again, I can change "Output Device"
  again and sound plays again for 5 seconds and then it is turned off.

  I play sound using my display built in device connected through HDMI
  cable and also using audio cable. Sound is not working through HDMI
  cable. It is working using audio cable or headphones.

  My expectation is, when I set output device to be audio cable - it
  will not be changed to HDMI cable.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lmlich 1369 F pulseaudio
   /dev/snd/pcmC1D0c:   lmlich 1369 F...m pulseaudio
   /dev/snd/pcmC1D0p:   lmlich 1369 F...m pulseaudio
   /dev/snd/controlC0:  lmlich 1369 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 21:09:40 2020
  InstallationDate: Installed on 2019-12-27 (82 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulseAudioLog:
   bře 18 21:02:14 lmquiet dbus-daemon[770]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.42' (uid=125 pid=979 comm="/usr/bin/pulseaudio --daemonize=no 
" label="unconfined")
   bře 18 21:02:31 lmquiet systemd[972]: pulseaudio.service: Succeeded.
   bře 18 21:02:42 lmquiet systemd[972]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [, Realtek ALC283, Black Headphone Out, Left] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0354.2016.0120.0912
  dmi.board.name: NUC5i3RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H41000-503
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0354.2016.0120.0912:bd01/20/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i3RYB:rvrH41000-503:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working

2020-04-24 Thread hackel

Same for me.
❯ ubuntu-drivers devices
== /sys/devices/pci:00/:00:1c.0/:3b:00.0 ==
modalias : pci:v8086d2723sv1A56sd1654bc02sc80i00
vendor   : Intel Corporation
model: Wi-Fi 6 AX200
manual_install: True
driver   : backport-iwlwifi-dkms - distro free

I do not even have backport-iwlwifi-dkms installed. iwlwifi is working
fine.

iwlwifi :3b:00.0: Detected Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless
Network Adapter (200NGW), REV=0x340

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

Title:
  software-properties-gtk erroneously reports that Intel Wireless-AC
  9260 device is not working

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-04-24 Thread Jane Atkinson

The following has me wondering if this has partly to do with the
presence of containers, VMs and similar items.

I upgraded my router to 20.04 a few days before release. (Plain Ubuntu
command-line OS on a PC Engines APU1 board) That machine has a bridge
network comprising two ethernets and one wifi. I've had no problems with
it - it comes up nicely on boot. Whereas I have to use the crontab
workaround on my main PC which has a bridge for VMs.

I'm not clever enough to imagine why this might be the case, but I
thought it might be worth noting.

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service;

[Touch-packages] [Bug 1874941] [NEW] lag and hangs

2020-04-24 Thread Jofen Kihlström

Public bug reported:

Since upgrading from ubuntu 18.04 I have not been able to stream video
from youtube without the video freezing for a second or two every 30
seconds. Also when filling out this form the text lag. This has not been
the case on this computer when using 18.04, 19.04 or 19.10.

This performance issue renders the computer hard to use for work and I
am almost completly certain that it is xorg or some other graphics
issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 25 01:52:12 2020
DistUpgraded: 2020-04-23 23:49:11,187 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
MachineType: HUAWEI MACH-WX9
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=e5a15015-60f2-4474-a116-bd9e25289d5f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)
dmi.bios.date: 03/15/2019
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.28
dmi.board.name: MACH-WX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M13
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M13
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13:
dmi.product.family: MateBook X
dmi.product.name: MACH-WX9
dmi.product.sku: C189
dmi.product.version: M13
dmi.sys.vendor: HUAWEI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal performance 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/1874941

Title:
  lag and hangs

Status in xorg package in Ubuntu:
  New

Bug description:
  Since upgrading from ubuntu 18.04 I have not been able to stream video
  from youtube without the video freezing for a second or two every 30
  seconds. Also when filling out this form the text lag. This has not
  been the case on this computer when using 18.04, 19.04 or 19.10.

  This performance issue renders the computer hard to use for work and I
  am almost completly certain that it is xorg or some other graphics
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 01:52:12 2020
  DistUpgraded: 2020-04-23 23:49:11,187 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=e5a15015-60f2-4474-a116-bd9e25289d5f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M13
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13:
  dmi.product.family: MateBook X
  dmi.product.name:

[Touch-packages] [Bug 1874942] [NEW] Seg fault when continue with breakpoint

2020-04-24 Thread Sitao Wang

Public bug reported:

I am able to run the program without seg fault and just run the program
in gdb does not have seg fault. However, when I set the some specific
breakpoint (but not every possible breakpoint), and then run program,
seg fault will happen on some other line than the breakpoint after some
continues.

Bellow is the trace:

GNU gdb (Ubuntu 8.2-0ubuntu1~16.04.1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/anygroup/go-repro/909_ziptest_exe2...done.
warning: File "/home/anygroup/go-repro/909-go/src/pkg/runtime/runtime-gdb.py" 
auto-loading has been declined by your `auto-load safe-path' set to 
"$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path 
/home/anygroup/go-repro/909-go/src/pkg/runtime/runtime-gdb.py
line to your configuration file "/home/anygroup/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/anygroup/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
(gdb) br *0x409398
Breakpoint 1 at 0x409398: file 
/home/anygroup/go-repro/909-go/src/pkg/runtime/mgc0.c, line 135.
(gdb) run test.zip
Starting program: /home/anygroup/go-repro/909_ziptest_exe2 test.zip

Breakpoint 1, 0x00409398 in scanblock (b=, 
n=) at 
/home/anygroup/go-repro/909-go/src/pkg/runtime/mgc0.c:135
135 obj = (void*)((uintptr)obj & 
~((uintptr)PtrSize-1));
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
scanblock (b=, n=)
at /home/anygroup/go-repro/909-go/src/pkg/runtime/mgc0.c:141
141 xbits = *bitp;

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

** Attachment added: "binary and a zip file used as program input"
   
https://bugs.launchpad.net/bugs/1874942/+attachment/5359929/+files/ziptest.zip

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

Title:
  Seg fault when continue with breakpoint

Status in gdb package in Ubuntu:
  New

Bug description:
  I am able to run the program without seg fault and just run the
  program in gdb does not have seg fault. However, when I set the some
  specific breakpoint (but not every possible breakpoint), and then run
  program, seg fault will happen on some other line than the breakpoint
  after some continues.

  Bellow is the trace:

  GNU gdb (Ubuntu 8.2-0ubuntu1~16.04.1) 8.2
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /home/anygroup/go-repro/909_ziptest_exe2...done.
  warning: File "/home/anygroup/go-repro/909-go/src/pkg/runtime/runtime-gdb.py" 
auto-loading has been declined by your `auto-load safe-path' set to 
"$debugdir:$datadir/auto-load".
  To enable execution of this file add
add-auto-load-safe-path 
/home/anygroup/go-repro/909-go/src/pkg/runtime/runtime-gdb.py
  line to your configuration file "/home/anygroup/.gdbinit".
  To completely disable this security protection add
set auto-load safe-path /
  line to your configuration file "/home/anygroup/.gdbinit".
  For more information about this security protection see the
  "Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
  (gdb) br *0x409398
  Breakpoint 1 at 0x409398: file 
/home/anygroup/go-repro/909-go/src/pkg/runtime/mgc0.c, line 135.
  (gdb) run test.zip
  Starting

[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage

2020-04-24 Thread Gregory

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

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

Title:
  Definition of add_mountroot_fail_hook doesnt match lvm2's usage

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Package lvm2 contains a init-premount script named /usr/share
  /initramfs-tools/scripts/init-premount/lvm2

  In this script there is the function call:
  add_mountroot_fail_hook "20-lvm2"

  Which is defined in /usr/share/initramfs-tools/scripts/functions

  In focal's 0.136ubuntu6 , this is defined as:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
  }

  The final line of the function will execute as
  ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"

  And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
  not exist.

  It is clear from lvm2's invocation that it expects the symlink to be
  named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
  the case:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
  }

  focal's version needs to be updated to either support the "$1"
  argument or strip the directory from "$0".

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

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

[Touch-packages] [Bug 1784163] Re: gnome-initial-setup hangs enabling livepatch

2020-04-24 Thread Navjot

I can confirm that this issue is still present in Ubuntu 20.04.

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

Title:
  gnome-initial-setup hangs enabling livepatch

Status in gnome-initial-setup package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I just upgraded from Artful to Bionic. gnome-initial-setup ran. It
  asked me if I wanted to enable Livepatch, and I agreed. I believe my
  Internet connection was working fine at the time. It gave me a
  username/password prompt. After entering those in it asked me for a
  2FA code. After entering that in, I got a spinner with "Connecting..."
  in the bottom left, but nothing further happens. It's been about ten
  minutes hung like that.

  I tried to click the Cancel button but nothing happened. Then I tried
  to close the app from the bar on the left (right click -> Quit) but
  nothing happened.

  After the previous actions, netstat reports no TCP connections on IPv4
  nor IPv6. It's appears not to be "Connecting" to anything.

  Expected: at least some kind of timeout reporting failure so I can
  progress with any other "initial setup" actions.

  A few things about my installation:

  I installed this laptop with Artful initially, around the beta1
  milestone. I dist upgraded it to Artful after release. Before
  upgrading to Bionic I made sure it was fully up to date.

  apport-bug didn't work. After I click Send, I got no browser prompt to
  finish my report. This might be because I have an unusual Firefox
  setup (multiple profiles).

  I noticed that I have bionic-proposed enabled. This is unintentional.
  It seems likely that I had artful-proposed enabled for test purposes
  previously. I did have a pin deprioritising it, but it refers to
  artful specifically so doesn't seem to have acted on Bionic, so
  unfortunately I've ended up upgrading all the way up to bionic-
  proposed.

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

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

[Touch-packages] [Bug 1848643] Re: [Huawei Matebook 13, Realtek ALC256, Black Headphone Out, Right] No sound at all

2020-04-24 Thread Gong Chen

Thanks Daniel. It works for me.

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

Title:
  [Huawei Matebook 13, Realtek ALC256, Black Headphone Out, Right] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  it can not automatic switching between speakers and headphone.
  The question is similar 
with:https://community.clearlinux.org/t/automatic-switching-between-speakers-and-headphones/916

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gong   1212 F pulseaudio
   /dev/snd/pcmC0D0c:   gong   1212 F...m pulseaudio
   /dev/snd/pcmC0D0p:   gong   1212 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 18 15:45:57 2019
  InstallationDate: Installed on 2019-10-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gong   1212 F pulseaudio
   /dev/snd/pcmC0D0c:   gong   1212 F...m pulseaudio
   /dev/snd/pcmC0D0p:   gong   1212 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [WRT-WX9, Realtek ALC256, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.19
  dmi.board.name: WRT-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1020
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.19:bd08/12/2019:svnHUAWEI:pnWRT-WX9:pvrM1020:rvnHUAWEI:rnWRT-WX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
  dmi.product.family: MateBook
  dmi.product.name: WRT-WX9
  dmi.product.sku: C233
  dmi.product.version: M1020
  dmi.sys.vendor: HUAWEI

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

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

[Touch-packages] [Bug 1874925] [NEW] Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

2020-04-24 Thread Adam Dyess

Public bug reported:

Internal Microphone doesn't show up as an audio source.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  addyess   106482 F pulseaudio
 /dev/snd/controlC1:  addyess   106482 F pulseaudio
 /dev/snd/controlC0:  addyess   106482 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Fri Apr 24 16:56:54 2020
InstallationDate: Installed on 2019-11-05 (171 days ago)
InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 863F
dmi.board.vendor: HP
dmi.board.version: 54.13
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
dmi.product.sku: 8LK66UA#ABA
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal

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

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

2020-04-24 Thread Adam Dyess

full hardware profile: https://linux-
hardware.org/index.php?probe=c17da47049

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

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1873528] Re: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order

2020-04-24 Thread Seth Arnold

On Fri, Apr 24, 2020 at 01:16:31PM -, Dimitri John Ledkov wrote:
> Include /run/ssh/sshd_config.d/*conf
> Include /etc/ssh/sshd_config.d/*conf
> Include /lib/ssh/sshd_config.d/*conf

> It would be nice if /etc/ssh only had the host keys, and no other
> default options.

This feels like it'd also need systemd-style config options to allow
admins to say they don't want specific packaged configs, too.

This mechanism could be ideal for eg ec2-instance-connect, except the
current implementation, via:
/lib/systemd/system/ssh.service.d/ec2-instance-connect.conf
can be ignored via a symlink to /dev/null in
/etc/systemd/system/ssh.service.d/ec2-instance-connect.conf

Changing to sshd config snippets in /lib/ssh/sshd_config.d/ would now
require uninstalling the package entirely, which might also require
uninstalling meta-packages.

A simple 'include' mechanism without allowances for nulling out unwanted
configs is useful but probably not alone sufficient.

Thanks

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

Title:
  sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse
  lexographic order

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf'
  for use in Ubuntu cloud images.  I wanted to add a config file and see
  if I had done things correctly.  I assumed that the files were sourced
  lexographically (based on use of glob() in readconf.h) so that I could
  document how users could override our tuning.  But it appears from
  'sshd -T' output and observed behavior that the first file in
  /etc/sshd_config.d/ to define a parameter wins.  I see in 'sshd -ddd'
  output that they are parsed lexographically but it seems that their
  settings apply in reverse (or whichever comes first) if that makes
  sense.  I'd like to understand if this is correct behavior and get it
  documented.

  Steps to reproduce on focal with openssh-server 1:8.2p1-4:

  1. Create the following files in /etc/ssh/sshd_config.d/ with the content 
shown below:
  40-cloudimg-settings.conf:
ClientAliveInterval 110
PasswordAuthentication yes
PermitRootLogin no

  50-cloudimg-settings.conf:
ClientAliveInterval 120
PermitRootLogin yes

  60-cloudimg-settings.conf:
ClientAliveInterval 180

  2. Check what sshd thinks the values will be with 'sshd -T|grep -i 
clientaliveinterval' and 'sshd -T|grep permitrootlogin'
  clientaliveinterval 110
  permitrootlogin no

  (The tuning I cared about was ClientAliveInterval for my work but
  PermitRootLogin is easier to demonstrate)

  3. Run '/usr/sbin/sshd -ddd' to check debug output for config file parsing 
behavior:
  debug2: load_server_config: filename /etc/ssh/sshd_config
  debug2: load_server_config: done config len = 296
  debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 296
  debug2: /etc/ssh/sshd_config line 13: new include 
/etc/ssh/sshd_config.d/*.conf
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf
  debug2: load_server_config: done config len = 71
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/40-cloudimg-settings.conf len 71
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:1 setting 
ClientAliveInterval 110
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:2 setting 
PasswordAuthentication yes
  debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:3 setting 
PermitRootLogin no
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf
  debug2: load_server_config: done config len = 46
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/50-cloudimg-settings.conf len 46
  debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:1 setting 
ClientAliveInterval 120
  debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:2 setting 
PermitRootLogin yes
  debug2: /etc/ssh/sshd_config line 13: including 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf
  debug2: load_server_config: filename 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf
  debug2: load_server_config: done config len = 25
  debug2: parse_server_config_depth: config 
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf len 25
  debug3: /etc/ssh/sshd_config.d/60-cloudimg-settings.conf:1 setting 
ClientAliveInterval 180

  4. Set a root password and unlock the account.

  5. Attempt to ssh as root to the instance with a password.

  Observation:
   * Root password login is denied if PermitRootLogin is 'no' in 40-foo.conf 
and 'yes' in 50-foo.conf
   * Root password login is allowed if PermitRootLogin is 'yes' in 40-foo.conf 
and 'no' in

[Touch-packages] [Bug 1874914] Re: screen size too big / title bar on second screen

2020-04-24 Thread Sebastien Bacher

Thank you for your bug report. Do you use your second screen as rotated?
Sounds a bit similar to bug #1874567. Do you get the issue if you
disable the nvidia binary driver?

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  screen size too big / title bar on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The title bar stretches ~1/2 way onto the second screen.
  Also when I move the mouse to the right the whole screen scrolls the width of 
the overlap.
  Picture attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 14:00:34 2020
  DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-46-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
   virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2018-05-23 (702 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=6aabc146-ac5f-4072-a83d-2cdc70d0615f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-207
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-207:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1874717] Re: devices cannot connect to ubuntu hotspot

2020-04-24 Thread Sebastien Bacher

Could you add the journal log?

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

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1865411] Re: Need to restart Network Manager frequently

2020-04-24 Thread Daniel

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

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => 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/1865411

Title:
  Need to restart Network Manager frequently

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My WiFi connection keeps stopping to work every once in a while
  (sometimes as often as every 10 minutes).

  Restarting NetworkManager usually resolves this problem. But I am not
  sure why that is the case. I do not think there is a connectivity
  issue as it happens even when I am right next to the access point.

  I have a standard Intel Wireless chip and use GNOME shell with some
  extensions. Nothing exotic.

  Note this happened on eoan as well as focal (and maybe even before
  that).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.8-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  1 19:56:11 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-07-09 (236 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.24 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/fish
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.8   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-04-24 Thread David Bridson

I'm experiencing the same problem on a fresh install of Ubuntu Mate
20.04 on a Dell XPS 13 9350.

Sound works correctly using the internal speakers. If you plug in analog
headphones to the 3.5mm jack, there is no sound from the headphones or
the internal speakers. All relevant options are unmuted in Sound
Settings. The Speaker Test exhibits the same behaviour.

Analog headphones worked correctly on this system under 18.04.

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

Title:
External audio device shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker, or none at
all.

Status in gnome-control-center:
Unknown
Status in PulseAudio:
New
Status in gnome-control-center package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
In Progress
Status in gnome-control-center source package in Focal:
Invalid
Status in pulseaudio source package in Focal:
In Progress

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

1. Connect an audio interface. I tried with BT headphones and speakers as
well as a USB microphone/output.
2. Make sure it's the one selected as "Output device"
3. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
4. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
5. Try to switch back to the BT device and click Test
-> same result as in step 3

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

Up to this morning, it was harder to connect the BT device, but once
connected, the sound would output on it as expected. Now, the BT
connection seems to work better, but I can't output the sound to the
BT device...

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output
from the internal laptop speakers, even when the BT device is selected
in the Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pieq 1566 F pulseaudio
/dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio
/dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread Mathew Hodson

** Tags removed: verification-needed

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

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

[Touch-packages] [Bug 1874914] [NEW] screen size too big / title bar on second screen

2020-04-24 Thread anderson.de...@gmail.com

Public bug reported:

The title bar stretches ~1/2 way onto the second screen.
Also when I move the mouse to the right the whole screen scrolls the width of 
the overlap.
Picture attached.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 14:00:34 2020
DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.3.0-46-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
 virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701]
InstallationDate: Installed on 2018-05-23 (702 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=6aabc146-ac5f-4072-a83d-2cdc70d0615f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
dmi.bios.date: 12/04/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67GD
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10206-207
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-207:cvn:ct3:cvr:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "picture of screen size error"
   
https://bugs.launchpad.net/bugs/1874914/+attachment/5359828/+files/IMG_20200424_140123.jpg

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

Title:
  screen size too big / title bar on second screen

Status in xorg package in Ubuntu:
  New

Bug description:
  The title bar stretches ~1/2 way onto the second screen.
  Also when I move the mouse to the right the whole screen scrolls the width of 
the overlap.
  Picture attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 14:00:34 2020
  DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-46-generic, x86_64: installed
   nvidia, 440.64,

Re: [Touch-packages] [Bug 1872842] Re: PCI/internal sound card not detected

2020-04-24 Thread Michael

Follow-up, and bug can be closed, hardware issue.

For the record, I do think that the frustration in the original bug 
report does point out that there is a need for a low level testing tool, 
to help identify if it is an actual hardware issue, or a problem with 
detection, or the drivers etc..

Out of frustration, I ended up calling the vendor (Lenovo) and while I 
haven't been happy with their hardware historically, and don't laugh 
that I ended up buying a ThinkCentre for a Linux station, I was 
pleasantly surprised with their support.

I was able to get a hold of a human almost right away, but I do think 
that Lenovo has a known hardware issue, that they only tell people about 
if they call for support.  AS soon as I mentioned 'audio' problems, he 
surprised me by not questioning it at all, and that 'they would send a 
technician out to replace the motherboard'.

(I thought he would at least put me through a testing song and dance, 
but no, no questions asked.. 4 minutes later off the phone)

Took about 10 days, but true to their word, motherboard was shipped, and 
technician showed up, replaced the motherboard, and all sound devices 
detected on boot, immediately.  (No changes need to sound configuration)

I guess it passes the hardware compatability with 16.04 ;)

Thanks all for your comments though.. but consider that some form of 
'testing' tool, should have come to the conclusion this was a hardware 
issue and saved me a few days of learning low level alsa/sound.

On 2020-04-14 5:44 p.m., Hui Wang wrote:
> Is there an audio enable option in the BIOS? Maybe it is disabled?
> 
> Or the codec is damaged physically? You could install the newer kernel
> to verify if the codec is good or not, if it is good and newer kernel
> could work, then we will bisect the kernel to find the fix for this
> issue.
>

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Upsstream says try a newer kernel, but I am on the LTS HWE kernels for
  Xenial, and want to solve this on this version.  This is a Think
  Centre M710e Model/Type 10UR, and the snd_hba_intel correctly loads,
  but finds no codecs.  This is the onboard audio card, and don't think
  they have chnaged it much in years, so I expect that at least SOME
  codecs should be detected.  Played with various alsa conf settings, no
  joy..

  options snd-hda-intel single_cmd=1
  options snd-hda-intel probe_mask=1
  options snd-hda-intel model=thinkpad
  options snd-hda-intel position_fix=3

  Tried model(s) generic, and auto.. always the same in bootup..

  [   12.684107] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [   12.827419] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0
  [   12.830129] snd_hda_intel :00:1f.3: no codecs found!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr 14 15:00:59 2020
  InstallationDate: Installed on 2019-11-03 (163 days ago)
  InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190226)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1ZKT23A
  dmi.board.name: 313C
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305181519567
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1ZKT23A:bd06/05/2018:svnLENOVO:pn10UR001JUS:pvrThinkCentreM710e:rvnLENOVO:rn313C:rvrSDK0J40697WIN3305181519567:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710e
  dmi.product.name: 10UR001JUS
  dmi.product.version: ThinkCentre M710e
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-13T16:09:19.881423

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

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

[Touch-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Norbert

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

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1088131] Re: ls --color doesn't recognize an arc archive as an archive

2020-04-24 Thread zapman

** Changed in: coreutils (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  ls --color doesn't recognize an arc archive as an archive

Status in coreutils:
  Fix Released
Status in coreutils package in Ubuntu:
  Fix Released

Bug description:
  When listing the content of a directory with ls --color an arc archive
  isn't recognized as an such and isn't displayed with the appropriate
  colour. The following terminal output should give an idea:

  ubuntu@ubuntu:~/test$ ls
  sources.list
  ubuntu@ubuntu:~/test$ tar cfz sources.taz sources.list
  ubuntu@ubuntu:~/test$ arc a sources.arc sources.list
  Creating new archive: sources.arc
  Adding file:   sources.list   analyzing, crunched, done. (29%)
  ubuntu@ubuntu:~/test$ ls
  sources.arc  sources.list  sources.taz

  Note that sources.taz would be correctly displayed in red, but not
  sources .arc which nevertheless is an archive and should also be
  displayed with the same colour. So the $LS_COLORS environment variable
  needs to be adjusted accordingly by default (the correct value to add
  would probably be "01;31", and arc is absent from the output of
  dircolors -p).

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: coreutils 8.13-3ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
  Uname: Linux 3.2.0-29-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CasperVersion: 1.315
  Date: Sun Dec  9 06:33:54 2012LiveMediaBuild: Ubuntu 12.04.1 LTS "Precise 
Pangolin" - Release i386 (20120817.3)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

2020-04-24 Thread Andrey Sapozhnikov

Focal release is affected as well.

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

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

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

[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp

2020-04-24 Thread Christoph Ziebuhr

This is the full log:
Apr 23 09:51:00 ct-prod systemd[1]: Stopping Network Service...
Apr 23 09:51:00 ct-prod systemd[1]: systemd-networkd.service: Succeeded.
Apr 23 09:51:00 ct-prod systemd[1]: Stopped Network Service.
Apr 23 09:51:00 ct-prod systemd[1]: Starting Network Service...
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Bus bus-api-network: changing 
state UNSET → OPENING
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Bus bus-api-network: changing 
state OPENING → AUTHENTICATING
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: timestamp of 
'/etc/systemd/network' changed
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: timestamp of 
'/run/systemd/network' changed
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: No virtualization found in DMI
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Virtualization found, 
CPUID=KVMKVMKVM
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Found VM virtualization kvm
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: 
/usr/lib/systemd/network/80-container-host0.network: Conditions in the file do 
not match the system environment, skipping.
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Flags change: +UP 
+LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Link 18378 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: udev initialized 
link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Saved original 
MTU: 1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Flags change: +UP 
+LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Link 18376 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: udev initialized 
link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Saved original 
MTU: 1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Flags change: +UP 
+LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Link 18374 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: udev initialized 
link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Saved original 
MTU: 1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: New device has 
no master, continuing without
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Flags change: 
+UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Link 18372 
added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: udev 
initialized link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Saved original 
MTU: 1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: New device has no 
master, continuing without
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Flags change: +UP 
+MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Link 3 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: udev initialized link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Saved original MTU: 
1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: New device has no master, 
continuing without
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Flags change: +UP 
+LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Link 2 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: udev initialized link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Saved original MTU: 1420
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: New device has no master, 
continuing without
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Flags change: +LOOPBACK +UP 
+LOWER_UP +RUNNING
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Link 1 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: udev initialized link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Saved original MTU: 65536
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Adding address: 
fe80::c0e2:b6ff:fec5:c370/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Gained IPv6LL
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Adding address: 
fe80::bc1c:baff:fedf:f0ef/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Gained IPv6LL
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Adding address: 
fe80::d84f:edff:fe33:55a0/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Gained IPv6LL
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Adding 
address: fe80::42:45ff:fed1:a3c2/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Gained IPv6LL
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Adding address: 
fe80::4001:aff:fea4:2/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Gained IPv6LL
Apr 23 09:51:00 ct-prod

[Touch-packages] [Bug 1874871] Re: Wrong screen offset dual monitors

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

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

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

Title:
  Wrong screen offset dual monitors

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I change screen position in gnome-settings, or reboot computer screens 
overlap.
  I have 2 monitors 1920x1080 @ 120Hz and 1280x1024@60 rotated to right. I use 
nvidia drivers 440.64, if I change the offset there, the problem is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:55:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02]
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_efifg2@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_efifg2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  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.:bvrP3.90:bd12/09/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4: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.sku: 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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1874887] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

2020-04-24 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev
  package post-installation script subprocess returned error exit status
  1

Status in systemd package in Ubuntu:
  New

Bug description:
  this was generated by a report

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   udev:amd64: Install
   libudev1:amd64: Install
   libudev1:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.subtitle-edit.rules 
70-snap.core.rules 70-snap.minetest.rules 70-snap.mc-installer.rules
  Date: Fri Apr 24 10:09:35 2020
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-04-17 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: ASUSTeK COMPUTER INC. N56VV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=185a0301-89b3-4798-b58b-80794b55d1b7 ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VV.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VV.201:bd06/05/2013:svnASUSTeKCOMPUTERINC.:pnN56VV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N56VV
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-04-24 Thread Sylvain Le Blanc

I have this exact bug after upgrading from 19.10 workstation to 20.04,
please notice I use the workstation has a LXD container server, all my
nfs mount point failed to mount, and I also never get an Ip address on
my bridge interface, to fix this manually I have todo netplan apply and
mount -a !

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 1650 (systemd-network)
   Status:

[Touch-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Gökhan K .

Sorry for all, "Fix Released" information for status isn't true, it's my
mistake.

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Gökhan K .

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874887] [NEW] package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

2020-04-24 Thread Iulian-Nicu Șerbănoiu

Public bug reported:

this was generated by a report

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: udev 245.4-4ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
AptOrdering:
 udev:amd64: Install
 libudev1:amd64: Install
 libudev1:amd64: Configure
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.subtitle-edit.rules 
70-snap.core.rules 70-snap.minetest.rules 70-snap.mc-installer.rules
Date: Fri Apr 24 10:09:35 2020
ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2020-04-17 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: ASUSTeK COMPUTER INC. N56VV
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=185a0301-89b3-4798-b58b-80794b55d1b7 ro quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: systemd
Title: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VV.201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VV.201:bd06/05/2013:svnASUSTeKCOMPUTERINC.:pnN56VV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N56VV
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package focal

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev
  package post-installation script subprocess returned error exit status
  1

Status in systemd package in Ubuntu:
  New

Bug description:
  this was generated by a report

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   udev:amd64: Install
   libudev1:amd64: Install
   libudev1:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.subtitle-edit.rules 
70-snap.core.rules 70-snap.minetest.rules 70-snap.mc-installer.rules
  Date: Fri Apr 24 10:09:35 2020
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-04-17 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: ASUSTeK COMPUTER INC. N56VV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=185a0301-89b3-4798-b58b-80794b55d1b7 ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VV.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VV.201:bd06/05/2013:svnASUSTeKCOMPUTERINC.:pnN56VV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N56VV
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Gökhan K .

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

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

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

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

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

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

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874880] [NEW] error running apt-add-repository

2020-04-24 Thread Edson T. Marques

Public bug reported:

today I accepted apt upgrades of some ubuntu repositories to Groove, after that 
I tried to add a new repo and got this messages:
 
root@etm:/etc/apt/sources.list.d# apt-add-repository ppa:linuxuprising/apps
Traceback (most recent call last):
  File "/usr/bin/apt-add-repository", line 107, in 
sp = SoftwareProperties(options=options)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
self.reload_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
  File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
raise NoDistroTemplateException(
aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/groovy

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apt 2.0.2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 15:18:26 2020
InstallationDate: Installed on 2020-01-28 (87 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  error running apt-add-repository

Status in apt package in Ubuntu:
  New

Bug description:
  today I accepted apt upgrades of some ubuntu repositories to Groove, after 
that I tried to add a new repo and got this messages:
   
  root@etm:/etc/apt/sources.list.d# apt-add-repository ppa:linuxuprising/apps
  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 107, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
  raise NoDistroTemplateException(
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/groovy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:18:26 2020
  InstallationDate: Installed on 2020-01-28 (87 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp

> 09:51:00 ens4: Configured
> 21:50:59 ens4: DHCP lease lost

er, did you happen to trim a few lines between those?  Can you please
provide the full unedited log?

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

Title:
  networkd sometimes doesn't set mtu received by dhcp

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
  GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
  I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.

  Log (filtered for ens4, some columns removed for better readability):
  09:51:00 ens4: New device has no master, continuing without
  09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
  09:51:00 ens4: Link 2 added
  09:51:00 ens4: udev initialized link
  09:51:00 ens4: Saved original MTU: 1420
  09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever)
  09:51:00 ens4: Gained IPv6LL
  09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: 
n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Link state is up-to-date
  09:51:00 ens4: found matching network 
'/run/systemd/network/10-netplan-ens4.network'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0'
  09:51:00 ens4: Started LLDP.
  09:51:00 ens4: Setting address genmode for link
  09:51:00 ens4: Setting address genmode done.
  09:51:00 ens4: Removing address 10.164.0.2
  09:51:00 ens4: Acquiring DHCPv4 lease
  09:51:00 ens4: Discovering IPv6 routers
  09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  09:51:00 ens4: Setting MTU: 1460
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  09:51:00 ens4: IPv6 successfully enabled
  09:51:00 ens4: Setting MTU done.
  09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d)
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configured
  21:50:59 ens4: DHCP lease lost
  21:50:59 ens4: Removing address 10.164.0.2
  21:50:59 ens4: Setting MTU: 1420
  21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  21:50:59 ens4: IPv6 successfully enabled
  21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s)
  21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Setting MTU done.
  21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d)
  21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configured

  On dhcp renew (09:51:00), mtu got properly changed to 1460.
  On next dhcp renew (21:50:59) it got changed back to previous value 1420.
  In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460.

  There have been some changes to mtu handling in the past, I assume
  this is a regression, potentially from
  https://github.com/systemd/systemd/issues/12552 or

[Touch-packages] [Bug 1874814] Re: ubuntu 20.04 non spegne il pc

2020-04-24 Thread samuele

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

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

Title:
  ubuntu 20.04 non spegne il pc

Status in systemd package in Ubuntu:
  New

Bug description:
  il 23 aprile, verso le ore 22:00 ho installato Ubuntu 20.04 sul mio
  notebook HP 250 G3 (con SSD)

  Ho notato fin da subito che quando arresto o lo riavvio il pc
  dall'interfaccia grafica, il pc non si spegne, rimane fissa la
  schermata logo HP con al di sotto la scritta "ubuntu". Il led di
  accensione del computer rimane fisso, mentre quello del caricamento
  resta sempre spento. Non mi resta che spegnere il pc tenendo premuto
  il tasto di spegnimento.

  Ho provato a spegnerlo da terminale con "sudo shutdown now" e mi è
  apparsa la seguente stringa, senza mai caricare altro.

  Foto: https://ibb.co/fMtymjT

  Ho provato a digitare "sudo init 0" e mi appare una schermata nera con
  un trattino basso fisso.

  Ho provato anche a spegnere da terminale tty1 sempre con "sudo
  shutdown now" allego foto:

  Foto: https://ibb.co/YbGRpwp

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

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

[Touch-packages] [Bug 1874871] [NEW] Wrong screen offset dual monitors

2020-04-24 Thread Lukáš Eret

Public bug reported:

When I change screen position in gnome-settings, or reboot computer screens 
overlap.
I have 2 monitors 1920x1080 @ 120Hz and 1280x1024@60 rotated to right. I use 
nvidia drivers 440.64, if I change the offset there, the problem is resolved.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:06:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 19:55:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02]
InstallationDate: Installed on 2020-04-23 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_efifg2@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_efifg2 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.90
dmi.board.name: B450M Pro4
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.:bvrP3.90:bd12/09/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4: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.sku: 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.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "Image of overlapping"
   
https://bugs.launchpad.net/bugs/1874871/+attachment/5359708/+files/IMG_20200424_200414.jpg

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

Title:
  Wrong screen offset dual monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  When I change screen position in gnome-settings, or reboot computer screens 
overlap.
  I have 2 monitors 1920x1080 @ 120Hz and 1280x1024@60 rotated to right. I use 
nvidia drivers 440.64, if I change the offset there, the problem is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:55:09

[Touch-packages] [Bug 1874814] [NEW] ubuntu 20.04 non spegne il pc

You have been subscribed to a public bug:

il 23 aprile, verso le ore 22:00 ho installato Ubuntu 20.04 sul mio
notebook HP 250 G3 (con SSD)

Ho notato fin da subito che quando arresto o lo riavvio il pc
dall'interfaccia grafica, il pc non si spegne, rimane fissa la schermata
logo HP con al di sotto la scritta "ubuntu". Il led di accensione del
computer rimane fisso, mentre quello del caricamento resta sempre
spento. Non mi resta che spegnere il pc tenendo premuto il tasto di
spegnimento.

Ho provato a spegnerlo da terminale con "sudo shutdown now" e mi è
apparsa la seguente stringa, senza mai caricare altro.

Foto: https://ibb.co/fMtymjT

Ho provato a digitare "sudo init 0" e mi appare una schermata nera con
un trattino basso fisso.

Ho provato anche a spegnere da terminale tty1 sempre con "sudo shutdown
now" allego foto:

Foto: https://ibb.co/YbGRpwp

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


** Tags: bot-comment
-- 
ubuntu 20.04 non spegne il pc
https://bugs.launchpad.net/bugs/1874814
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1874819] Re: Cannot change display driver in Software & Updates

Replaced by https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874856,
to include the Xorg logs.

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

Title:
  Cannot change display driver in Software & Updates

Status in software-properties package in Ubuntu:
  New

Bug description:
  Fresh 20.04 install: after changing from proprietary nvidia 440 driver
  to nouveau and restart, the Software & Updates does not allow me to
  change back to the proprietary drivers, as the buttons are now greyed
  out.

  Workaround:
  sudo ubuntu-drivers devices  # shows available drivers
  sudo apt install nvidia-driver-440

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:20:08 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874856] Re: Unwanted mouse trail

** Attachment removed: "mousetrail.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874856/+attachment/5359627/+files/mousetrail.jpg

** Attachment added: "mousetrail.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874856/+attachment/5359700/+files/mousetrail.jpg

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

Title:
  Unwanted mouse trail

Status in xorg package in Ubuntu:
  New

Bug description:
  Moving mouse leaves a trail of squares for a few seconds on a fresh
  20.04 install. This happens with proprietary nvidia 440 drivers as
  well as nouveau on my GeFOrce GTX 1050 mobile.

  Could be related to my submission
  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/1874819

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:59:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1a10]
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. X580VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X580VD.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X580VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X580VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri Apr 24 16:45:55 2020
  xserver.configfile: default
  xserver.errors:
   NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver
   NVIDIA(G0): Failing initialization of X screen
   systemd-logind: failed to release device: Device not taken
   systemd-logind: failed to release device: Device not taken
   modeset(0): failed to set mode: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1874862] [NEW] Touch inputs not detected

2020-04-24 Thread Will Ethridge

Public bug reported:

touch inputs are not detected by Ubuntu on this tablet. I'm not sure the
touch screen hardware is detected at all by Ubuntu. I tried cat
/dev/input/eventX (replacing X with every option listed) and not once
got any reaction to touching the screen.

I can provide more information and troubleshooting if asked, I just need
to know what to look for.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.5.0-050500-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 13:27:45 2020
DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
InstallationDate: Installed on 2020-01-22 (92 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0603:0002 Novatek Microelectronics Corp. 
 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
 |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
 |__ Port 2: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
MachineType: MicroElectronics TW102
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic 
root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-01-26 (88 days ago)
dmi.bios.date: 03/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8.17
dmi.board.asset.tag: Default string
dmi.board.name: H8811C
dmi.board.vendor: EMDOOR
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: EMDOOR
dmi.chassis.version: 1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1:
dmi.product.family: WinBook
dmi.product.name: TW102
dmi.product.sku: 585497
dmi.product.version: 1
dmi.sys.vendor: MicroElectronics
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1874862

Title:
  Touch inputs not detected

Status in xorg package in Ubuntu:
  New

Bug description:
  touch inputs are not detected by Ubuntu on this tablet. I'm not sure
  the touch screen hardware is detected at all by Ubuntu. I tried cat
  /dev/input/eventX (replacing X with every option listed) and not once
  got any reaction to touching the screen.

  I can provide more information and troubleshooting if asked, I just
  need to know what to look for.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.5.0-050500-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 13:27:45 2020
  DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

** Tags added: block-proposed-bionic block-proposed-eoan block-proposed-
focal

** Changed in: network-manager (Ubuntu Eoan)
   Status: Won't Fix => In Progress

** Changed in: network-manager (Ubuntu Focal)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Bionic)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: network-manager (Ubuntu Eoan)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  In Progress
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-24 Thread Kelsey Margarete Skunberg

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

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you
  have grub2 2.02-2ubuntu8.15 installed.

  Shut the VM down, and set the video device to VGA. Or VGA=std if you
  use the QEMU command line.

  Start the VM up, and the screen will be garbled. See attached picture.

  If you install my test packages, which are available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test

  Instructions to install (on a bionic system):

  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020

  If you reboot, the screen will be perfectly readable, since the bochs-
  drm driver will be in

[Touch-packages] [Bug 1870427] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-04-24 Thread Mikko

Same issue occurred here during 19.10 -> 20.04 upgrade.

Configuration file '/etc/default/smartmontools'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** smartmontools (Y/I/N/O/D/Z) [default=N] ? D
sh: 1: pager: not found
diff: standard output: Broken pipe

Pager worked fine during the upgrade with packages before and after
smartmontools.

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

Title:
  package smartmontools 7.1-1build1 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

Status in dpkg package in Ubuntu:
  Incomplete
Status in less package in Ubuntu:
  Confirmed

Bug description:
  During an upgrade from eoan to focal I got the following error:

   package:smartmontools:7.1-1build1
   Installing new version of config file /etc/init.d/smartmontools ...

   Configuration file '/etc/smartd.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
  What would you like to do about it ?  Your options are:
   Y or I  : install the package maintainer's version
   N or O  : keep your currently-installed version
 D : show the differences between the versions
 Z : start a shell to examine the situation
The default action is to keep your current version.
   *** smartd.conf (Y/I/N/O/D/Z) [default=N] ? d
   sh: 1: pager: not found
   diff: standard output: Broken pipe
   dpkg: error processing package smartmontools (--configure):
conffile difference visualizer subprocess returned error exit status 127

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: smartmontools 7.1-1build1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Thu Apr  2 19:58:06 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python3, 3.8.2-3
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: smartmontools
  Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  mtime.conffile..etc.smartd.conf: 2019-06-28T19:35:09.428956

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

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

[Touch-packages] [Bug 1870427] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

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

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

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

Title:
  package smartmontools 7.1-1build1 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

Status in dpkg package in Ubuntu:
  Incomplete
Status in less package in Ubuntu:
  Confirmed

Bug description:
  During an upgrade from eoan to focal I got the following error:

   package:smartmontools:7.1-1build1
   Installing new version of config file /etc/init.d/smartmontools ...

   Configuration file '/etc/smartd.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
  What would you like to do about it ?  Your options are:
   Y or I  : install the package maintainer's version
   N or O  : keep your currently-installed version
 D : show the differences between the versions
 Z : start a shell to examine the situation
The default action is to keep your current version.
   *** smartd.conf (Y/I/N/O/D/Z) [default=N] ? d
   sh: 1: pager: not found
   diff: standard output: Broken pipe
   dpkg: error processing package smartmontools (--configure):
conffile difference visualizer subprocess returned error exit status 127

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: smartmontools 7.1-1build1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Thu Apr  2 19:58:06 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python3, 3.8.2-3
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: smartmontools
  Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  mtime.conffile..etc.smartd.conf: 2019-06-28T19:35:09.428956

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

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

[Touch-packages] [Bug 1742804] Re: Failed to add PIDs to scope's control group

2020-04-24 Thread Bug Watch Updater

** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  Failed to add PIDs to scope's control group

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  [impact]

  systemd-run --user --scope fails

  [test case]

  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

  [regression potential]

  large.  this is fixed upstream by a large sequence of patches, and
  would need careful attention applying them all to make sure no
  regressions were introduced.

  If I, or anyone else, attempts this backport, they definitely need to
  add more detail to this section.

  [scope]

  This is fixed upstream by this large PR:
  https://github.com/systemd/systemd/pull/8125

  That's included starting in systemd v238, so just missed the Bionic
  version.  This is fixed already in all releases after Bionic, and
  needed only for Bionic.

  [original description]

  
  When I launch applications with flatpak, "journalctl -f" shows the following:

  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Failed to add PIDs to scope's control group: Permission denied
  Jan 11 22:44:13 localhost systemd[1244]: Failed to start 
flatpak-org.kde.krita-8134.scope.
  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Unit entered failed state.

  I explicitly mentioned "Kubuntu" in the summary, because I experience
  this only under Kubuntu (17.10 and 18.04), NOT under the regular
  Gnome-based Ubuntu Desktop (17.10). At first this error message seemed
  harmless, because it looked like it had no effect. But now I noticed
  that with certain flatpak apps, the file open dialog would not pop up.
  And I too experienced this only under Kubuntu, not Ubuntu or Fedora
  (all tested). So there might be a connection.

  I first reported this to flatpak:

  https://github.com/flatpak/flatpak/issues/1216

  There it was suggested to try the following command:

  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

  ...and this one also fails.

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

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

[Touch-packages] [Bug 1874861] [NEW] Xorg freeze

2020-04-24 Thread Stefano Coronado

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04


2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center

xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu14
  Version table:
 *** 1:7.7+19ubuntu14 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status


3) What you expected to happen

Being able to switch between "Frequent" and "All" within GNOME App menu

4) What happened instead


The screen froze
The screen not to freeze

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 13:18:07 2020
DistUpgraded: 2020-04-24 12:33:58,057 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: focal
DistroVariant: ubuntu
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
InstallationDate: Installed on 2019-06-09 (319 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Hewlett-Packard HP EliteBook 8470p
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=5523994d-c0c4-49a7-8e11-4d2ce9de39d9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
dmi.bios.date: 07/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICF Ver. F.43
dmi.board.name: 179B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.36
dmi.chassis.asset.tag: CNU2250G4C
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.43:bd07/16/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029CD1:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 8470p
dmi.product.sku: B8Q56UP
dmi.product.version: A1029CD1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze 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/1874861

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center

  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen

  Being able to switch between "Frequent" and "All" within GNOME App
  menu

  4) What happened instead

  
  The screen froze
  The screen not to freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 13:18:07 2020
  DistUpgraded: 2020-04-24 12:33:58,057 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

** Description changed:

  [Impact]
  
  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill block/unblock.
- Adding a sleep before calling nmcli fixes the issue.
  
  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz
  
  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -
  
  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18
  
  [Test Case]
  
  Assume that test vm and host are ppc64
  
  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi
  
  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled
  
  second 'enabled' should be 'disabled' but not updated properly.
  
  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.
  
  [Regression Potential]
  
- No regression potential. The fix touches only the testcase shipped with
- the source package and it doesn't change the binary package. The sleep
- time added is very small, so no possibility of causing testcase timeout.
+ This fixes testcase only, so any regression would cause incorrect test
+ pass/fail, and might cause other missed bugs.
+ 
+ [scope]
+ 
+ this is needed for all releases.  Debian does not include this
+ autopkgtest, and so does not need this fix.
  
  [Other Info]
+ 
+ this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
+ starting up 'systemd-rfkill.service' for any change.  On a 1-cpu system
+ (which all autopkgtest instances for network-manager are), this service
+ startup sometimes blocks the uevent from reaching network-manager before
+ the autopkgtest proceeds to call nmcli to check the rfkill status.  This
+ causes the test case to fail.
+ 
+ There are (at least) 2 options to fix this:
+ 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
+ 2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status
+ 
+ This does not need to be fixed outside the test case, as normal nmcli
+ use should be not done by users in a script immediately after changing
+ rfkill state, nor is there anything that either rfkill or nmcli could
+ even do to address this (technically, nmcli could internally issue a
+ 'udevadm settle' every time it's called, but that seems paranoid and
+ extreme).
+ 
+ [original description]
  
  On ppc64el architecture, it was observed that a fix for systemd is also
  needed (see bug 1734908) for the testcase to be successful.
  
  # original test case
  
  2.1. Download network-manager package source code
  $ apt-get source network-manager
  
  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

** Also affects: network-manager (Ubuntu Bionic)
   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/1733321

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:

[Touch-packages] [Bug 1874856] [NEW] Unwanted mouse trail

Public bug reported:

Moving mouse leaves a trail of squares for a few seconds on a fresh
20.04 install. This happens with proprietary nvidia 440 drivers as well
as nouveau on my GeFOrce GTX 1050 mobile.

Could be related to my submission
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/1874819

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 17:59:48 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10]
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1a10]
InstallationDate: Installed on 2020-04-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK COMPUTER INC. X580VD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X580VD.315
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X580VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: X580VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
nvidia-settings:
 ERROR: Unable to load info from any available system
 
 
 ERROR: Unable to load info from any available system
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Fri Apr 24 16:45:55 2020
xserver.configfile: default
xserver.errors:
 NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver
 NVIDIA(G0): Failing initialization of X screen
 systemd-logind: failed to release device: Device not taken
 systemd-logind: failed to release device: Device not taken
 modeset(0): failed to set mode: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.8-2ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "mousetrail.jpg"
   
https://bugs.launchpad.net/bugs/1874856/+attachment/5359627/+files/mousetrail.jpg

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

Title:
  Unwanted mouse trail

Status in xorg package in Ubuntu:
  New

Bug description:
  Moving mouse leaves a trail of squares for a few seconds on a fresh
  20.04 install. This happens with proprietary nvidia 440 drivers as
  well as nouveau on my GeFOrce GTX 1050 mobile.

  Could be related to my submission
  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/1874819

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""

[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage

2020-04-24 Thread lerxst

I'm noticing the same behavior. Please fix!

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

Title:
  Definition of add_mountroot_fail_hook doesnt match lvm2's usage

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Package lvm2 contains a init-premount script named /usr/share
  /initramfs-tools/scripts/init-premount/lvm2

  In this script there is the function call:
  add_mountroot_fail_hook "20-lvm2"

  Which is defined in /usr/share/initramfs-tools/scripts/functions

  In focal's 0.136ubuntu6 , this is defined as:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
  }

  The final line of the function will execute as
  ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"

  And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
  not exist.

  It is clear from lvm2's invocation that it expects the symlink to be
  named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
  the case:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
  }

  focal's version needs to be updated to either support the "$1"
  argument or strip the directory from "$0".

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

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

[Touch-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch

2020-04-24 Thread Olivier Tilloy

This sounds like a connectivity/network driver issue, rather than a
problem with thunderbird.

** Also affects: network-manager (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/1870111

Title:
  Thunderbird freezes graphical session except mouse cursor on second
  launch or clicking the icon after email setup on the first launch

Status in network-manager package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  When Launching thunderbird (pinned on Favourites) from the dock/dash
  it shows 2 orange dots on default theme that is one for email setup
  and the other for the main window. After setting up an email and
  closing the email config window, the two dots are still shown on the
  dash/dock before the icon. Thunderbird causes the graphical session
  except for the mouse cursor to freeze until I switch to a TTY and
  reboot. Also when closing thunderbird, one dot is shown and when
  launching the application the graphical session except for mouse
  cursor freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  BuildID: 20200110143530
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 13:26:59 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2020-03-31 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=68.4.1/20200110143530
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874515] Re: 20.04 does not bring up certain bridges

2020-04-24 Thread Mikael

Also noted behavior. After updating to 20.04 DHCP leases are not renewed
after boot. Unsure if related to above issues, but might be in the
ballpark.

Prior to the upgrade:

Apr 22 14:57:58 fancy dhclient[3068]: DHCPACK of 158.174.x.x from 212.116.x.x
Apr 22 19:35:49 fancy dhclient[3068]: DHCPREQUEST of 158.174.x.x on br_ext_prim 
to 212.116.x.x port 67 (xid=0x477b0bc1)
Apr 22 19:35:49 fancy dhclient[3068]: DHCPACK of 158.174.x.x from 212.116.x.x
Apr 23 01:25:50 fancy dhclient[3068]: DHCPREQUEST of 158.174.x.x on br_ext_prim 
to 212.116.x.x port 67 (xid=0x477b0bc1)
Apr 23 01:25:50 fancy dhclient[3068]: DHCPACK of 158.174.x.x from 212.116.x.x
Apr 23 07:21:56 fancy dhclient[3068]: DHCPREQUEST of 158.174.x.x on br_ext_prim 
to 212.116.x.x port 67 (xid=0x477b0bc1)
Apr 23 07:21:56 fancy dhclient[3068]: DHCPACK of 158.174.x.x from 212.116.x.x
Apr 23 12:08:44 fancy dhclient[3068]: DHCPREQUEST of 158.174.x.x on br_ext_prim 
to 212.116.x.x port 67 (xid=0x477b0bc1)
Apr 23 12:08:44 fancy dhclient[3068]: DHCPACK of 158.174.x.x from 212.116.x.x
Apr 23 16:50:09 fancy dhclient[3068]: DHCPREQUEST of 158.174.x.x on br_ext_prim 
to 212.116.x.x port 67 (xid=0x477b0bc1)
Apr 23 16:50:09 fancy dhclient[3068]: DHCPACK of 158.174.x.x from 212.116.x.x

Like clockwork.


After upgrade:

Apr 23 19:39:41 fancy audit[1053]: AVC apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 
comm="apparmor_parser"
Apr 23 19:39:41 fancy audit[1053]: AVC apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1053 comm="apparmor_parser"
Apr 23 19:39:42 fancy dhclient[1254]: Internet Systems Consortium DHCP Client 
4.4.1
Apr 23 19:39:42 fancy ifup[1254]: Internet Systems Consortium DHCP Client 4.4.1
Apr 23 19:39:42 fancy ifup[1254]: For info, please visit 
https://www.isc.org/software/dhcp/
Apr 23 19:39:42 fancy dhclient[1254]: For info, please visit 
https://www.isc.org/software/dhcp/
Apr 23 19:39:42 fancy ifup[1254]: DHCPDISCOVER on br_ext_prim to 
255.255.255.255 port 67 interval 3 (xid=0xfb894100)
Apr 23 19:39:42 fancy dhclient[1254]: DHCPDISCOVER on br_ext_prim to 
255.255.255.255 port 67 interval 3 (xid=0xfb894100)
Apr 23 19:39:45 fancy dhclient[1254]: DHCPDISCOVER on br_ext_prim to 
255.255.255.255 port 67 interval 4 (xid=0xfb894100)
Apr 23 19:39:45 fancy ifup[1254]: DHCPDISCOVER on br_ext_prim to 
255.255.255.255 port 67 interval 4 (xid=0xfb894100)
Apr 23 19:39:49 fancy dhclient[1254]: DHCPDISCOVER on br_ext_prim to 
255.255.255.255 port 67 interval 7 (xid=0xfb894100)
Apr 23 19:39:49 fancy ifup[1254]: DHCPDISCOVER on br_ext_prim to 
255.255.255.255 port 67 interval 7 (xid=0xfb894100)
Apr 23 19:39:50 fancy dhclient[1254]: DHCPOFFER of 158.174.x.x from 
212.116.65.157
Apr 23 19:39:50 fancy ifup[1254]: DHCPOFFER of 158.174.x.x from 212.116.65.157
Apr 23 19:39:50 fancy ifup[1254]: DHCPREQUEST for 158.174.x.x on br_ext_prim to 
255.255.255.255 port 67 (xid=0x4189fb)
Apr 23 19:39:50 fancy dhclient[1254]: DHCPREQUEST for 158.174.x.x on 
br_ext_prim to 255.255.255.255 port 67 (xid=0x4189fb)
Apr 23 19:39:50 fancy dhclient[1254]: DHCPACK of 158.174.x.x from 
212.116.65.157 (xid=0xfb894100)
Apr 23 19:39:50 fancy ifup[1254]: DHCPACK of 158.174.x.x from 212.116.65.157 
(xid=0xfb894100)

No additional logs after yesterday at 19:39:50. The lease expired today
at 07:39:50 and the primary network connection died.

Nothing more exceptional than restarting dhclient. Still annoying. Maybe
related.

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

Title:
  20.04 does not bring up certain bridges

Status in ifupdown package in Ubuntu:
  New

Bug description:
  After upgrading from a fully patched ubuntu-server 18.04 to 20.04 and
  rebooting I noticed that some of my bridge interfaces defined in
  /etc/network/interfaces would not come up while others would.

  Bridges brought up at boot:

  br_ext_prim
  br_ext_sec
  br_int_50
  br_nat

  Bridges missing:

  br_int_500
  br_nat_ext

  
  Relevant log from 18.04 prior to upgrade:

  Apr 23 19:11:37 fancy systemd-udevd[725]: Could not generate persistent MAC 
address for br_nat_ext: No such file or directory
  Apr 23 19:11:37 fancy systemd[1]: Found device 
/sys/subsystem/net/devices/br_nat_ext.
  Apr 23 19:11:37 fancy systemd[1]: Started ifup for br_nat_ext.
  Apr 23 19:11:37 fancy systemd-networkd[2284]: br_nat_ext: Link UP
  Apr 23 19:11:37 fancy sh[2383]: Waiting for br_nat_ext to get ready (MAXWAIT 
is 5 seconds).
  Apr 23 19:11:37 fancy kernel: [9.447538] br_nat_ext: port 1(int0.51) 
entered blocking state
  Apr 23 19:11:37 fancy kernel: [9.447540] br_nat_ext: port 1(int0.51) 
entered disabled state
  Apr 23 19:11:37 fancy systemd-networkd[2284]: br_nat_ext: Gained carrier
  Apr 23 19:11:37 fancy kernel: [   10.942682] br_nat_ext: port

[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH

2020-04-24 Thread klogg

Bug persists in xubuntu 20.04 - checked with fresh install today:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal

$ bash --version
GNU bash, version 5.0.16(1)-release (x86_64-pc-linux-gnu)

must be reopened

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

Title:
  Please add ~/.local/bin to the default $PATH

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Xenial:
  Fix Released
Status in bash package in Debian:
  Fix Released

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

[Touch-packages] [Bug 1874716] Re: Changing screen brightness fails

2020-04-24 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Changing screen brightness fails

Status in xorg package in Ubuntu:
  New

Bug description:
  Lenovo Legion with Nvidia card:

  FN+F5/F6 shows brightness changes, but the screen actually doesn't
  change at all.

  01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce
  GTX 1650 Mobile / Max-Q] (rev a1)

  nvidia  20430848  538 nvidia_uvm,nvidia_modeset
  nvidia_drm 45056  8
  nvidia_modeset   1114112  12 nvidia_drm
  nvidia_uvm966656  0
  nvme   49152  2
  nvme_core 102400  4 nvme

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 06:23:22 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3ffb]
  InstallationDate: Installed on 2020-03-12 (42 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: LENOVO 81T2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=51068ea2-6b38-4cfc-a75f-4f404cd04685 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN35WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1874846] Re: Xorg or more likely kernel/driver freeze

2020-04-24 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Xorg or more likely kernel/driver freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  The symptoms are that I am working normally, often with a remmina
  remote session open and suddenly everything stops. The keyboard will
  no longer response (caps-lock and Alt/SysRQ/reisub both have no
  effect. This started with kernel vmlinuz-5.3.0-46-generic and my
  current workaround is tu drop back to the previous -45 kernel which
  has been solid for about 4 weeks of fairly intense remote working.

  I think it is possibly another instance of existing bug 1872292 and
  I'm keen to help get you any diagnostic information I reasonably can.

  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  Chris Ritson

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Apr 24 16:43:08 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2020-03-23 (32 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0031.2015.0601.1712
  dmi.board.name: NUC5PPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H76558-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0031.2015.0601.1712:bd06/01/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5PPYB:rvrH76558-102:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1874851] [NEW] Unable to remove file or folder from desktop using key or dropdown menu interface

2020-04-24 Thread Norbert

Public bug reported:

Steps to reproduce:
1. Have Ubuntu 20.04 LTS installed
2. Open terminal and create new file and new folder

 mkdir ~/Desktop/folder
 touch ~/Desktop/file

3. Close terminal
4. Locate *folder* and *file* on the desktop, then
4.1. Press 
4.2. Do right mouse click on each and try to find Delete/Remove menu item


Expected results:
* user is able to remove object from Desktop by mouse or keyboard

Actual results:
* user is unable to remove object from Desktop by mouse or keyboard

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-desktop 1.450
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 19:07:36 2020
InstallationDate: Installed on 2020-04-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874846] [NEW] Xorg or more likely kernel/driver freeze

You have been subscribed to a public bug:

The symptoms are that I am working normally, often with a remmina remote
session open and suddenly everything stops. The keyboard will no longer
response (caps-lock and Alt/SysRQ/reisub both have no effect. This
started with kernel vmlinuz-5.3.0-46-generic and my current workaround
is tu drop back to the previous -45 kernel which has been solid for
about 4 weeks of fairly intense remote working.

I think it is possibly another instance of existing bug 1872292 and I'm
keen to help get you any diagnostic information I reasonably can.

Description:Ubuntu 18.04.4 LTS
Release:18.04

Chris Ritson

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CompositorRunning: None
Date: Fri Apr 24 16:43:08 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
InstallationDate: Installed on 2020-03-23 (32 days ago)
InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PYBSWCEL.86A.0031.2015.0601.1712
dmi.board.name: NUC5PPYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H76558-102
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0031.2015.0601.1712:bd06/01/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5PPYB:rvrH76558-102:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
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

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


** Tags: amd64 apport-bug bionic freeze ubuntu
-- 
Xorg or more likely kernel/driver freeze
https://bugs.launchpad.net/bugs/1874846
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1874716] [NEW] Changing screen brightness fails

You have been subscribed to a public bug:

Lenovo Legion with Nvidia card:

FN+F5/F6 shows brightness changes, but the screen actually doesn't
change at all.

01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce
GTX 1650 Mobile / Max-Q] (rev a1)

nvidia  20430848  538 nvidia_uvm,nvidia_modeset
nvidia_drm 45056  8
nvidia_modeset   1114112  12 nvidia_drm
nvidia_uvm966656  0
nvme   49152  2
nvme_core 102400  4 nvme

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 06:23:22 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3ffb]
InstallationDate: Installed on 2020-03-12 (42 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
MachineType: LENOVO 81T2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=51068ea2-6b38-4cfc-a75f-4f404cd04685 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: BHCN35WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Y545 PG0
dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:
dmi.product.family: Legion Y545 PG0
dmi.product.name: 81T2
dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
dmi.product.version: Legion Y545 PG0
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
Changing screen brightness fails 
https://bugs.launchpad.net/bugs/1874716
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1874819] Re: Cannot change display driver in Software & Updates

** Description changed:

  Fresh 20.04 install: after changing from proprietary nvidia 440 driver
  to nouveau and restart, then the Software & Updates does not allow me to
  change back to the proprietary drivers, as the buttons are now greyed
  out.
+ 
+ Workaround:
+ sudo ubuntu-drivers devices  # shows available drivers
+ sudo apt install nvidia-driver-440
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:20:08 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Fresh 20.04 install: after changing from proprietary nvidia 440 driver
- to nouveau and restart, then the Software & Updates does not allow me to
+ to nouveau and restart, the Software & Updates does not allow me to
  change back to the proprietary drivers, as the buttons are now greyed
  out.
  
  Workaround:
  sudo ubuntu-drivers devices  # shows available drivers
  sudo apt install nvidia-driver-440
- 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:20:08 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Cannot change display driver in Software & Updates

Status in software-properties package in Ubuntu:
  New

Bug description:
  Fresh 20.04 install: after changing from proprietary nvidia 440 driver
  to nouveau and restart, the Software & Updates does not allow me to
  change back to the proprietary drivers, as the buttons are now greyed
  out.

  Workaround:
  sudo ubuntu-drivers devices  # shows available drivers
  sudo apt install nvidia-driver-440

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:20:08 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1742804] Re: Failed to add PIDs to scope's control group

Hi, sorry this was reported before I subscribed to systemd bugs.

This does still affect Bionic, so I targeted the bug for that release;
this should be fixed already in all releases after Bionic.

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

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

** Description changed:

- When I launch applications with flatpak, "journalctl -f" shows the
- following:
+ [impact]
+ 
+ systemd-run --user --scope fails
+ 
+ [test case]
+ 
+ $ systemd-run --user --scope echo hello
+ Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
+ See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.
+ 
+ [regression potential]
+ 
+ large.  this is fixed upstream by a large sequence of patches, and would
+ need careful attention applying them all to make sure no regressions
+ were introduced.
+ 
+ If I, or anyone else, attempts this backport, they definitely need to
+ add more detail to this section.
+ 
+ [scope]
+ 
+ This is fixed upstream by this large PR:
+ https://github.com/systemd/systemd/pull/8125
+ 
+ That's included starting in systemd v238, so just missed the Bionic
+ version.  This is fixed already in all releases after Bionic, and needed
+ only for Bionic.
+ 
+ [original description]
+ 
+ 
+ When I launch applications with flatpak, "journalctl -f" shows the following:
  
  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Failed to add PIDs to scope's control group: Permission denied
  Jan 11 22:44:13 localhost systemd[1244]: Failed to start 
flatpak-org.kde.krita-8134.scope.
  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Unit entered failed state.
  
  I explicitly mentioned "Kubuntu" in the summary, because I experience
  this only under Kubuntu (17.10 and 18.04), NOT under the regular Gnome-
  based Ubuntu Desktop (17.10). At first this error message seemed
  harmless, because it looked like it had no effect. But now I noticed
  that with certain flatpak apps, the file open dialog would not pop up.
  And I too experienced this only under Kubuntu, not Ubuntu or Fedora (all
  tested). So there might be a connection.
  
  I first reported this to flatpak:
  
  https://github.com/flatpak/flatpak/issues/1216
  
  There it was suggested to try the following command:
  
  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.
  
  ...and this one also fails.

** Bug watch added: github.com/systemd/systemd/issues #3388
   https://github.com/systemd/systemd/issues/3388

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/3388
   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/1742804

Title:
  Failed to add PIDs to scope's control group

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  [impact]

  systemd-run --user --scope fails

  [test case]

  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

  [regression potential]

  large.  this is fixed upstream by a large sequence of patches, and
  would need careful attention applying them all to make sure no
  regressions were introduced.

  If I, or anyone else, attempts this backport, they definitely need to
  add more detail to this section.

  [scope]

  This is fixed upstream by this large PR:
  https://github.com/systemd/systemd/pull/8125

  That's included starting in systemd v238, so just missed the Bionic
  version.  This is fixed already in all releases after Bionic, and
  needed only for Bionic.

  [original description]

  
  When I launch applications with flatpak, "journalctl -f" shows the following:

  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Failed to add PIDs to scope's control group: Permission denied
  Jan 11 22:44:13 localhost systemd[1244]: Failed to start 
flatpak-org.kde.krita-8134.scope.
  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Unit entered failed state.

  I explicitly mentioned "Kubuntu" in the summary, because I experience
  this only under Kubuntu (17.10 and 18.04), NOT under the regular
  Gnome-based Ubuntu Desktop (17.10). At first this error message seemed
  harmless, because it looked like it had no effect. But now I noticed
  that with certain flatpak apps, the file open dialog would not pop up.
  And I too experienced this only under Kubuntu, not Ubuntu or Fedora
  (all

[Touch-packages] [Bug 1874707] Re: [DICE - FW610, playback] Rhythmic Clicking sound when playing audio, like sync issue on 20.04

2020-04-24 Thread onur çetinkol

I edited because I thought it's started after upgrading to 20.04, but I
checked and 19.10 also has the problem but it is much less noticeable.

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

Title:
  [DICE - FW610, playback] Rhythmic Clicking sound when playing audio,
  like sync issue on 20.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When audio source output is above average, there are rhythmic clicking
  sounds. The audio quailty is also not as good as on Windows and there
  are random low hissing and noises.

  When I open a sine wave audio file from 0hz to 20khz and clicking gets
  louder when frequency gets higher. It is not audible below 600hz, and
  strongest at 20khz. Btw clicking speed is not changing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  realiti7133 F pulseaudio
   /dev/snd/controlC0:  realiti7133 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 14:23:03 2020
  InstallationDate: Installed on 2020-02-10 (73 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:FW610 failed
  Symptom_Card: ProFire 610 - FW610
  Symptom_PulseAudioLog:
   Nis 24 14:04:27 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=124 pid=1245 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   Nis 24 14:04:33 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.69' (uid=1000 pid=1683 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Nis 24 14:11:32 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.121' (uid=1000 pid=7133 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [DICE - FW610, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  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.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1874836] [NEW] Xrandr says that hdmi is disconnected but it was not.

2020-04-24 Thread Lefevre

Public bug reported:

Just after a reboot my second screen stop being recognized.

I ran xrandr command and the result was that the hdmi cable was
disconnected, but it wasn't.

I assume it come from the xrandr lib but i'm not sure at all

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libxrandr2 2:1.5.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 17:11:35 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
InstallationDate: Installed on 2020-04-23 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FJS12100
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=cf7e310d-b6c4-4e10-b62b-3ac6b016f210 ro quiet splash vt.handoff=7
SourcePackage: libxrandr
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1KET21W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FJS12100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS12100:pvrThinkPadT560:rvnLENOVO:rn20FJS12100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T560
dmi.product.name: 20FJS12100
dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
dmi.product.version: ThinkPad T560
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Xrandr says that hdmi is disconnected but it was not.

Status in libxrandr package in Ubuntu:
  New

Bug description:
  Just after a reboot my second screen stop being recognized.

  I ran xrandr command and the result was that the hdmi cable was
  disconnected, but it wasn't.

  I assume it come from the xrandr lib but i'm not sure at all

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libxrandr2 2:1.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:11:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-04-23 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS12100
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=cf7e310d-b6c4-4e10-b62b-3ac6b016f210 ro quiet splash vt.handoff=7
  SourcePackage: libxrandr
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS12100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined

[Touch-packages] [Bug 1874707] Re: [DICE - FW610, playback] Rhythmic Clicking sound after upgrading from 19.10 to 20.04

2020-04-24 Thread onur çetinkol

I narrowed down the problem I believe. I opened a sine wave audio file
from 0hz to 20khz and clicking gets louder when frequency gets higher.
It is not audible below 600hz, and strongest at 20khz. Btw clicking
speed is not changing.

** Summary changed:

- [DICE - FW610, playback] Rhythmic Clicking sound after upgrading from 19.10 
to 20.04
+ [DICE - FW610, playback] Rhythmic Clicking sound when playing audio, like 
sync issue on 20.04

** Description changed:

- After upgrading to 20.04, when audio source output is above average,
- there are rhythmic clicking sounds. The audio quailty is also bad
- compared to 19.10 and there are random low hissing and noises.
+ When audio source output is above average, there are rhythmic clicking
+ sounds. The audio quailty is also not as good as on Windows and there
+ are random low hissing and noises.
+ 
+ When I open a sine wave audio file from 0hz to 20khz and clicking gets
+ louder when frequency gets higher. It is not audible below 600hz, and
+ strongest at 20khz. Btw clicking speed is not changing.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  realiti7133 F pulseaudio
-  /dev/snd/controlC0:  realiti7133 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  realiti7133 F pulseaudio
+  /dev/snd/controlC0:  realiti7133 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 14:23:03 2020
  InstallationDate: Installed on 2020-02-10 (73 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:FW610 failed
  Symptom_Card: ProFire 610 - FW610
  Symptom_PulseAudioLog:
-  Nis 24 14:04:27 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=124 pid=1245 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
-  Nis 24 14:04:33 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.69' (uid=1000 pid=1683 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
-  Nis 24 14:11:32 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.121' (uid=1000 pid=7133 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
+  Nis 24 14:04:27 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=124 pid=1245 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
+  Nis 24 14:04:33 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.69' (uid=1000 pid=1683 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
+  Nis 24 14:11:32 realiti-ubuntu dbus-daemon[1074]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.121' (uid=1000 pid=7133 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [DICE - FW610, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 03/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3802
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  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.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  [DICE - FW610, playback] Rhythmic Clicking sound when playing audio,
  like sync issue on 20.04

Status in alsa-driver package in Ubuntu:

[Touch-packages] [Bug 1874832] [NEW] QCoreApplications sets QTextCodec::codecForLocale() incorrectly

2020-04-24 Thread tom stevens

Public bug reported:

With ICU versions >= 61 QTextCodec::codecForLocale() always returns the
utf-8 codec with mib 106 regardless of the value of the environmental
variable LC_ALL or the available locales.

On bionic, which included ICU 60, codecForLocale() returned the correct
codec.  On eoan and focal, which include ICU 63 and ICU 66, the utf-8
codec is always returned.

The change in behavior is expected due to a documented change in ICU 
https://github.com/unicode-org/icu/commit/d7482c9720b4f71dd9dad0.
However, Qt has not accounted for this change in ICU.

I note that Qt 5.12.8 from
https://download.qt.io/archive/qt/5.12/5.12.8/ is packaged with an older
version of ICU so the combination works correctly.  But on Ubuntu eoan
and focal the included version of ICU is not compatible with the
included Qt.

The included file localetrouble.tar contains
1) demo: a script that builds two tests cases and runs them
2) focal.log: the results of running the demo script on focal
3) bionic.log: the results of running the demo script on bionic
4) test1.cc: a minimal Qt Core application that tries to use the codec from the 
current locale.
5) test1.pro: Qt pro file used to build test1.cc
6) test2.cc: a test program that shows why Qt fails to detect the correct 
locale.  These two lines are executed by QCoreApplicationPrivate::initLocale() 
and *QIcuCodec::defaultCodecUnlocked().
7) test2.pro: Qt pro file used to build test2.cc

The expected results of test1 are that codecForLocale is set based on LC_ALL to 
en_US.iso88591:
env LC_ALL=en_US.iso88591 ./test1
QTextCodec::codecForLocale():  "ISO-8859-1" , mib 4
LC_ALL:  en_US.iso88591

The actual results on focal are:
env LC_ALL=en_US.iso88591 ./test1
QTextCodec::codecForLocale():  "UTF-8" , mib 106
LC_ALL:  en_US.iso88591

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: qtbase5-dev 5.12.8+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 24 14:45:36 2020
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
SourcePackage: qtbase-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "bug demonstration and analysis"
   
https://bugs.launchpad.net/bugs/1874832/+attachment/5359537/+files/localetrouble.tar

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

Title:
  QCoreApplications sets QTextCodec::codecForLocale() incorrectly

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  With ICU versions >= 61 QTextCodec::codecForLocale() always returns
  the utf-8 codec with mib 106 regardless of the value of the
  environmental variable LC_ALL or the available locales.

  On bionic, which included ICU 60, codecForLocale() returned the
  correct codec.  On eoan and focal, which include ICU 63 and ICU 66,
  the utf-8 codec is always returned.

  The change in behavior is expected due to a documented change in ICU 
https://github.com/unicode-org/icu/commit/d7482c9720b4f71dd9dad0.
  However, Qt has not accounted for this change in ICU.

  I note that Qt 5.12.8 from
  https://download.qt.io/archive/qt/5.12/5.12.8/ is packaged with an
  older version of ICU so the combination works correctly.  But on
  Ubuntu eoan and focal the included version of ICU is not compatible
  with the included Qt.

  The included file localetrouble.tar contains
  1) demo: a script that builds two tests cases and runs them
  2) focal.log: the results of running the demo script on focal
  3) bionic.log: the results of running the demo script on bionic
  4) test1.cc: a minimal Qt Core application that tries to use the codec from 
the current locale.
  5) test1.pro: Qt pro file used to build test1.cc
  6) test2.cc: a test program that shows why Qt fails to detect the correct 
locale.  These two lines are executed by QCoreApplicationPrivate::initLocale() 
and *QIcuCodec::defaultCodecUnlocked().
  7) test2.pro: Qt pro file used to build test2.cc

  The expected results of test1 are that codecForLocale is set based on LC_ALL 
to en_US.iso88591:
  env LC_ALL=en_US.iso88591 ./test1
  QTextCodec::codecForLocale():  "ISO-8859-1" , mib 4
  LC_ALL:  en_US.iso88591

  The actual results on focal are:
  env LC_ALL=en_US.iso88591 ./test1
  QTextCodec::codecForLocale():  "UTF-8" , mib 106
  LC_ALL:  en_US.iso88591

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: qtbase5-dev 5.12.8+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 14:45:36 2020
  ProcEnviron:

[Touch-packages] [Bug 1874051] Re: Crackling headphone output after waking up from sleep

2020-04-24 Thread jkelol111 [Nam]

I upgraded to Ubuntu 20.04, issue is persisting.

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

Title:
  Crackling headphone output after waking up from sleep

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have performed a fresh install of Ubuntu 18.04.4, Ubuntu 19.10, and
  Ubuntu 20.04, as well as Fedora 31 and all of them have this issue
  with this audio codec. On Windows 10, sound plays perfectly when
  waking from sleep, whereas on Ubuntu there is this strange 'crackling'
  sound that occurs when some playback is happening. Laptop is the HP
  Pavilion x360 Convertible 14-ba0xx.

  This issue seems very similar but it looks like no one is fixing it:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183

  (I can confirm Erikas' solution in the above bug thread works, there
  is no more crackling on resume from suspend)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jkelol111   1825 F pulseaudio
   /dev/snd/pcmC0D0p:   jkelol111   1825 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 19:17:10 2020
  InstallationDate: Installed on 2020-04-21 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulseAudioLog:
   Apr 21 09:32:13 BrokenHingeLaptop dbus-daemon[1006]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.34' (uid=124 pid=1196 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Apr 21 09:32:28 BrokenHingeLaptop systemd[1165]: pulseaudio.service: 
Succeeded.
   Apr 21 09:32:38 BrokenHingeLaptop systemd[1165]: pulseaudio.socket: 
Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [HP Pavilion x360 Convertible 14-ba0xx, Realtek ALC295, Black 
Headphone Out, Left] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.53
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 830F
  dmi.board.vendor: HP
  dmi.board.version: 31.25
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.53:bd05/03/2019:svnHP:pnHPPavilionx360Convertible14-ba0xx:pvrType1ProductConfigId:rvnHP:rn830F:rvr31.25:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-ba0xx
  dmi.product.sku: 2GV24PA#UUF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

** Description changed:

  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now
  "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers
  are working fine, I do not have the internal microphone working (suspect
  a digital array).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  wittawat   2063 F pulseaudio
-  /dev/snd/controlC0:  wittawat   2063 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  wittawat   2063 F pulseaudio
+  /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

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

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

[Touch-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

Okay. I will use "dsp_driver=1" for now then. Just for your information,
before I installed Ubuntu 20.04, I used 18.04. On 18.04, I tried a few
kernels on https://kernel.ubuntu.com/~kernel-ppa/mainline/ ranging from
5.3.x, 5.4.x, 5.5.x, 5.6.6 (I can't remember which x I tried anymore). I
got the same observation I reported here for both cases (with
dsp_driver=1 or without).

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

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

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

[Touch-packages] [Bug 1874821] [NEW] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2020-04-24 Thread Tim Dollowitch

Public bug reported:

[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun

I have screen flashing and some tearing on HP Elitebook Folio G1. Had
the same problem on 16.04 and 18.04. Previously was able to use
"i915.enable_rc6=0" on 16.04 and then "intel_idle.max_cstate=4" on 18.04
as workarounds. I'd like to help get to the bottom of this rather than a
work-around, but will need guidance to participate.

Description:Ubuntu 20.04 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 10:16:32 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
InstallationDate: Installed on 2020-04-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b58e Chicony Electronics Co., Ltd HP IR Camera
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 04f2:b58f Chicony Electronics Co., Ltd HP HD Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP EliteBook Folio G1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=3ef2b246-80ee-47da-ba11-fdfc1eef2362 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2020
dmi.bios.vendor: HP
dmi.bios.version: N91 Ver. 01.45
dmi.board.name: 8170
dmi.board.vendor: HP
dmi.board.version: KBC Version 29.73
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.45:bd01/05/2020:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook Folio G1
dmi.product.sku: P2C88AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1874821

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in xorg package in Ubuntu:
  New

Bug description:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

  I have screen flashing and some tearing on HP Elitebook Folio G1. Had
  the same problem on 16.04 and 18.04. Previously was able to use
  "i915.enable_rc6=0" on 16.04 and then "intel_idle.max_cstate=4" on
  18.04 as workarounds. I'd like to help get to the bottom of this
  rather than a work-around, but will need guidance to participate.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 10:16:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b58e Chicony Electronics Co., Ltd HP IR Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b58f

[Touch-packages] [Bug 1874824] [NEW] pgrep reports error "cannot allocate" when run without stack limit

2020-04-24 Thread Sven Hartrumpf

Public bug reported:

If you have no stack limit (ulimit -S -s unlimited), any pgrep call will
fail with an error:

> pgrep vim
pgrep: cannot allocate 4611686018427387903 bytes

If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very
slow:

> time pgrep vim
2196
real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
Archlinux bug report: https://bugs.archlinux.org/task/66093

procps:
  Installed: 2:3.3.16-1ubuntu2
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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


** Tags: focal

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  New

Bug description:
  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
Installed: 2:3.3.16-1ubuntu2
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Touch-packages] [Bug 1874819] [NEW] Cannot change display driver in Software & Updates

Public bug reported:

Fresh 20.04 install: after changing from proprietary nvidia 440 driver
to nouveau and restart, then the Software & Updates does not allow me to
change back to the proprietary drivers, as the buttons are now greyed
out.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.98.9
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 15:20:08 2020
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2020-04-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterpreterPath: /usr/bin/python3.8
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-04-24 15-27-20.png"
   
https://bugs.launchpad.net/bugs/1874819/+attachment/5359504/+files/Screenshot%20from%202020-04-24%2015-27-20.png

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

Title:
  Cannot change display driver in Software & Updates

Status in software-properties package in Ubuntu:
  New

Bug description:
  Fresh 20.04 install: after changing from proprietary nvidia 440 driver
  to nouveau and restart, then the Software & Updates does not allow me
  to change back to the proprietary drivers, as the buttons are now
  greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:20:08 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

2020-04-24 Thread Hui Wang

OK, there is at least one problem in the driver I know, and will build a
testing kernel, maybe next Monday.

Please use the workaround "dsp_driver=1" temporarily.

thx.

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

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

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

[Touch-packages] [Bug 1874812] [NEW] package mime-support 3.64ubuntu1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-04-24 Thread Niels Vanderschaeghe

Public bug reported:

just appeared when i booted my ubuntu 20.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mime-support 3.64ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 24 15:16:53 2020
ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
InstallationDate: Installed on 2019-12-10 (135 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: mime-support
Title: package mime-support 3.64ubuntu1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)

** Affects: mime-support (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package mime-support 3.64ubuntu1 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

Status in mime-support package in Ubuntu:
  New

Bug description:
  just appeared when i booted my ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 15:16:53 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  InstallationDate: Installed on 2019-12-10 (135 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: mime-support
  Title: package mime-support 3.64ubuntu1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)

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

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

[Touch-packages] [Bug 1874812] Re: package mime-support 3.64ubuntu1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-04-24 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package mime-support 3.64ubuntu1 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

Status in mime-support package in Ubuntu:
  New

Bug description:
  just appeared when i booted my ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 15:16:53 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  InstallationDate: Installed on 2019-12-10 (135 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: mime-support
  Title: package mime-support 3.64ubuntu1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)

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

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

[Touch-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

Full dmesg log. Remove "options snd-intel-dspcfg dsp_driver=1"

** Attachment added: "dont_add_dsp_driver1.log"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5359492/+files/dont_add_dsp_driver1.log

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

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

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

[Touch-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

Many thanks for your prompt response. If I remove, "options snd-intel-
dspcfg dsp_driver=1" from /etc/modprobe.d/alsa-base.conf, then on
pavucontrol, I see "Dummy Output" on the "Output Devices" tab and the
speakers will not work. Attaching alsa-info here:

http://alsa-project.org/db/?f=eef8051cb397d6b1240bbbc0a84d102928ec23c9



inxi -Fxz

System:Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Gnome 3.36.1 
   Distro: Ubuntu 20.04 LTS (Focal Fossa) 
Machine:   Type: Laptop System: HP product: OMEN by HP Laptop 15-dh0xxx v: N/A 
serial:  
   Mobo: HP model: 8600 v: 44.41 serial:  UEFI: AMI v: F.22 
date: 12/09/2019 
Battery:   ID-1: BAT1 charge: 70.1 Wh condition: 70.1/69.0 Wh (102%) model: 
COMPAL PABAS0241231 status: Full 
CPU:   Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP 
arch: Kaby Lake rev: A L2 cache: 12.0 MiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 62399 
   Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
   9: 800 10: 800 11: 800 12: 800 
Graphics:  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: 
Hewlett-Packard driver: nvidia v: 440.64 bus ID: 01:00.0 
   Display: x11 server: X.Org 1.20.8 driver: nvidia unloaded: 
fbdev,modesetting,nouveau,vesa 
   resolution: 1920x1080~144Hz 
   OpenGL: renderer: GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 440.64 
direct render: Yes 
Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard driver: 
sof-audio-pci bus ID: 00:1f.3 
   Device-2: NVIDIA TU106 High Definition Audio vendor: Hewlett-Packard 
driver: snd_hda_intel v: kernel 
   bus ID: 01:00.1 
   Sound Server: ALSA v: k5.4.0-26-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Hewlett-Packard driver: r8169 v: kernel 
   port: 3000 bus ID: 3c:00.0 
   IF: enp60s0 state: down mac:  
   Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 3000 
bus ID: 3e:00.0 
   IF: wlp62s0 state: up mac:  
Drives:Local Storage: total: 476.94 GiB used: 15.11 GiB (3.2%) 
   ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000H1 size: 
476.94 GiB 
RAID:  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: 
ahci v: 3.0 bus ID: 00:17.0 
Partition: ID-1: / size: 48.34 GiB used: 13.52 GiB (28.0%) fs: ext4 dev: 
/dev/nvme0n1p5 
   ID-2: /home size: 182.34 GiB used: 1.52 GiB (0.8%) fs: ext4 dev: 
/dev/nvme0n1p7 
   ID-3: swap-1 size: 37.81 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/nvme0n1p6 
Sensors:   System Temperatures: cpu: 49.0 C mobo: 10.0 C gpu: nvidia temp: 38 C 
   Fan Speeds (RPM): N/A 
Info:  Processes: 418 Uptime: 4m Memory: 15.51 GiB used: 2.68 GiB (17.3%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41

[Touch-packages] [Bug 1874717] nmcli-con.txt

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359464/+files/nmcli-con.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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://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 1874717] Re: devices cannot connect to ubuntu hotspot

-- Logs begin at Fri 2019-11-01 14:03:33 IST, end at Fri 2020-04-24
19:19:10 IS>
Apr 24 19:06:40 Hogwarts kernel: microcode: microcode updated early to
revision>
Apr 24 19:06:40 Hogwarts kernel: Linux version 5.4.0-26-generic
(buildd@lcy01-a>
Apr 24 19:06:40 Hogwarts kernel: Command line:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-2>
Apr 24 19:06:40 Hogwarts kernel: KERNEL supported cpus:
Apr 24 19:06:40 Hogwarts kernel:   Intel GenuineIntel
Apr 24 19:06:40 Hogwarts kernel:   AMD AuthenticAMD
Apr 24 19:06:40 Hogwarts kernel:   Hygon HygonGenuine
Apr 24 19:06:40 Hogwarts kernel:   Centaur CentaurHauls
Apr 24 19:06:40 Hogwarts kernel:   zhaoxin   Shanghai
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: Supporting XSAVE feature 0x001:
'x87 >
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: Supporting XSAVE feature 0x002:
'SSE >
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: Supporting XSAVE feature 0x004:
'AVX >
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: Supporting XSAVE feature 0x008:
'MPX >
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: Supporting XSAVE feature 0x010:
'MPX >
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: xstate_offset[2]:  576,
xstate_sizes[>
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: xstate_offset[3]:  832,
xstate_sizes[>
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: xstate_offset[4]:  896,
xstate_sizes[>
Apr 24 19:06:40 Hogwarts kernel: x86/fpu: Enabled xstate features 0x1f,
context>
Apr 24 19:06:40 Hogwarts kernel: BIOS-provided physical RAM map:
Apr 24 19:06:40 Hogwarts kernel: BIOS-e820: [mem
0x-0x0>
Apr 24 19:06:40 Hogwarts kernel: BIOS-e820: [mem
0x00058000-0x0>
Apr 24 19:06:40 Hogwarts kernel: BIOS-e820: [mem
0x00059000-0x0>

On Fri, 24 Apr 2020 at 18:50, Sebastien Bacher 
wrote:

> could you also add your 'journalctl -b 0' log to the bug after getting
> the issue and specify the time where you triggered the problem (to make
> easier to spot the right log section)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874717
>
> Title:
>   devices cannot connect to ubuntu hotspot
>
> Status in network-manager package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
>   based internet connection to my ubuntu system via the hotspot
>   connection to my other devices.I am able to connect to my hospot
>   though. My ethernet connection works fine hotspot too but my devices
>   report:"This device has no connection to internet."Earlier in v18.04
>   it worked fine.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: ubuntu-release-upgrader-core 1:20.04.18
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CrashDB: ubuntu
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr 24 17:49:30 2020
>   InstallationDate: Installed on 2019-06-18 (310 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   PackageArchitecture: all
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_IN
>SHELL=/bin/bash
>   SourcePackage: ubuntu-release-upgrader
>   Symptom: dist-upgrade
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   VarLogDistupgradeTermlog:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874717/+subscriptions
>

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

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN

[Touch-packages] [Bug 1874717] nmcli-dev.txt

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359465/+files/nmcli-dev.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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359463/+files/WifiSyslog.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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1874717] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1874717/+attachment/5359455/+files/RfKill.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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359454/+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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1874717] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359452/+files/PciNetwork.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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359453/+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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1874717] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359447/+files/IwConfig.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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1874717/+attachment/5359446/+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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1874717] NetDevice.wlp3s0.txt

apport information

** Attachment added: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359450/+files/NetDevice.wlp3s0.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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1874717] NetDevice.enp2s0.txt

apport information

** Attachment added: "NetDevice.enp2s0.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359448/+files/NetDevice.enp2s0.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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359449/+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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359451/+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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1874717/+attachment/5359445/+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/1874717

Title:
  devices cannot connect to ubuntu hotspot

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet
  based internet connection to my ubuntu system via the hotspot
  connection to my other devices.I am able to connect to my hospot
  though. My ethernet connection works fine hotspot too but my devices
  report:"This device has no connection to internet."Earlier in v18.04
  it worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:49:30 2020
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-18 (310 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 10.20.2.1 dev enp2s0 proto static metric 100 
   10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 
   10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 
   169.254.0.0/16 dev enp2s0 scope link metric 1000
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1874717] Re: devices cannot connect to ubuntu hotspot