[Touch-packages] [Bug 1863447] Re: openssh outdated by 8.2

2020-02-16 Thread Christian Ehrhardt 
Hi Hadmut,
we had the same discussion over the weekend if 8.2 would be good to have in 
20.04.

I subscribed cjwatson who usually does openssh updates to comment on his
intentions in this regard.

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

Title:
  openssh outdated by 8.2

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi,

  yeah, it's not yet a bug, but it will become a (security) bug within
  lifetime of 20.04 if not 'fixed'.

  Currently openssh for Ubuntu 20.04 is still on 8.1p1, while upstream
  the version 8.2 has just been released:

  https://lists.mindrot.org/pipermail/openssh-unix-
  announce/2020-February/000138.html

  It comes with important security updates, e.g. not accepting SHA-1 for
  key generation/signature anymore, and using FIDO2/U2F-tokens as a
  second factor. Especially the latter significantly improves security
  and helps against stealing keys and hijacking machines.

  It would be important (and nice) to have these improvements of
  security in Ubuntu 20.04.

  
  It might not yet be seen as a security vulnerability, but it will probably 
become one soon. 

  Thanks

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

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


[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

2020-02-16 Thread Daniel van Vugt
** Changed in: gtk
   Importance: Medium => Undecided

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

** Changed in: gtk
 Remote watch: GNOME Bug Tracker #692666 => None

** Bug watch added: bugzilla.gnome.org/ #692666
   https://bugzilla.gnome.org/show_bug.cgi?id=692666

** Changed in: gnome-control-center
   Importance: Medium => Unknown

** Changed in: gnome-control-center
 Remote watch: GNOME Bug Tracker #692666 => bugzilla.gnome.org/ #692666

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  New
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

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

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


[Touch-packages] [Bug 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user

2020-02-16 Thread Christian Ehrhardt 
** Merge proposal linked:
   
https://code.launchpad.net/~bryce/ubuntu/+source/openssh/+git/openssh/+merge/378685

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

Title:
  upgrade from fresh bionic to focal needlessly prompts user

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Fix Committed

Bug description:
  Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts
  for how to handle a change to /etc/ssh/sshd_config

  To reproduce the issue:

  lxc launch ubuntu:18.04 u18
  lxc exec u18 -- bash
  # within container
  do-release-upgrade -d
  # select restart services when prompted

  Eventually you'll be prompted to accept changes to
  /etc/ssh/sshd_config or not because of "local changes".

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.1p1-5
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 03:37:55 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: openssh
  UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago)

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

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


[Touch-packages] [Bug 970814] Re: Combobox badly initialized (semi-sensitive?) since gtk3

2020-02-16 Thread Launchpad Bug Tracker
[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Combobox badly initialized (semi-sensitive?) since gtk3

Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  My app uses a GTK3 ui created by Glade3.10.
  In the Glade file, there are some combobox with default "sensitive" settings 
(sensitive=yes), other with "non-sensitive" settings (sensitive=no)

  OBSERVED BEHAVIOR:
  When running my app (either in Ubuntu 11.10 or 12.04), all comboboxes 
(sensitive=yes or no) appear in what i will call "semi-sensitive" state: they 
behave like sensitive but their label is greyed (not the arrow, which is 
normally black, see attached screenshot).
  When the user moves the cursor above the combobox, the grey label becomes 
black (like a normal sensitive combobox).

  EXPECTED BEHAVIOR:
  the comboboxes should directly appear in the state chosen in the Glade file.

  
  WORKAROUND: 
  in the code of my app, i send a signal to set the state of the combobox as 
"sensitive" to make it sensitive at start. If i want the combobox to appear 
"non-sensitive" at start, i need to send a signal to set the state of the 
combobox as "sensitive" then another one to set it "non-sensitive".

  
  Remarks: 
  - don't hesitate to ask more informations, or link me to the right place.
  - with gtk2 my app does not have this bug

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

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


[Touch-packages] [Bug 1745984] Re: package update-notifier 3.168.7 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2020-02-16 Thread Launchpad Bug Tracker
[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package update-notifier 3.168.7 failed to install/upgrade: problemas
  de dependencias - se deja sin configurar

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: update-notifier 3.168.7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Jan 29 09:32:30 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2016-11-13 (442 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: update-notifier
  Title: package update-notifier 3.168.7 failed to install/upgrade: problemas 
de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.update-notifier.desktop: 2016-06-29T18:23:45

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

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


[Touch-packages] [Bug 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem

2020-02-16 Thread JamesH
I don't think that apport-collect will work while I am offline. Please
let me know how I can run this command and send the data after I have
done the restart. Remember, after restart the problem goes away. I can't
run diagnostics on Internet access that requires Internet access to run.
As it looks like I am talking to an automated script rather than a real
person perhaps this is now a dead thread.

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

Title:
  Ubuntu 18.04 and 19.04 new ethernet problem

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

Bug description:
  Ubuntu 19.04 (64 bit) on OptiPlex-7010
  On every power on I have no wired Ethernet connection or even an icon to 
enable it. After a restart (soft boot) it comes back again. This appears to be 
different from another bug reported which states that the Ethernet cable has to 
be unplugged during power on. In my issue, I can leave the Ethernet cable 
plugged in and it works fine. It just doesn't work during first power on boot.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-01-26 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.1.1 dev eno1 proto dhcp metric 100 
   169.254.0.0/16 dev eno1 scope link metric 1000 
   192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-74-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Wired connection 1  bea41631-df6c-3de0-ac4c-7606d1313303  ethernet  
1580229876  Tue 28 Jan 2020 08:44:36 AM PST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eno1ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  bea41631-df6c-3de0-ac4c-7606d1313303  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1856738] Re: access always denied when using @{HOME} tunable in peer_addr for abstract socket

2020-02-16 Thread John Johansen
This is due to how the VAR is expanded

assuming

  @{HOME}=/home/*/

then

  @@{HOME}/.cache/ibus/dbus-*"

expands to

  /home/*//.cache/ibus/dbus-*"


and currently the secondary pass to cleanup // is not being done because the 
code is treating addr as a profile name where // is a hierarchy separator. We 
can treat addr as a pathname so that the cleanup pass is done.

Long term we should make variable expansion smarter so that trailing /
in a var can not result in a // in the expansion.

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

Title:
  access always denied when using @{HOME} tunable in peer_addr for
  abstract socket

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  With this profile:

  #include 

  profile test {
#include 

# Parses but always denied
unix (connect, receive, send)
  type=stream
  peer=(addr="@@{HOME}/.cache/ibus/dbus-*"),

# parses and allows access
  #  unix (connect, receive, send)
  #type=stream
  #peer=(addr="@/home/*/.cache/ibus/dbus-*"),
  }

  In one terminal I start a server:
  $ ./abstract-server stream /home/jamie/.cache/ibus/dbus-foo

  Then in another terminal do:

  $ sudo apparmor_parser -r /tmp/apparmor.profile && aa-exec -p test -- 
./abstract-client stream /home/jamie/.cache/ibus/dbus-foo hi
  connect() failed

  With the following denial (and no output from the server terminal):
  apparmor="DENIED" operation="connect" profile="test" pid=3665 
comm="abstract-client" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive connect" denied_mask="send connect" addr=none 
peer_addr="@/home/jamie/.cache/ibus/dbus-fo" peer="unconfined"

  Commenting out the @{HOME} rule and uncommenting the /home/* rule, it
  works:

  $ sudo apparmor_parser -r /tmp/apparmor.profile && aa-exec -p test -- 
./abstract-client stream /home/jamie/.cache/ibus/dbus-foo hi
  MESSAGE FROM SERVER: received message number 1

  (with the server displaying 'MESSAGE FROM CLIENT: hi')

  Attached is the server and client code.

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

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


[Touch-packages] [Bug 1863455] Re: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28

2020-02-16 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Tags added: regression-update

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

Title:
  USB system (mouse and keybord) are not working since kernel update to
  5.3.0-26 and 5.3.0-28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. 
Keyboard and mouse (both connected via USB) are not working. It looks like 
everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the 
new kernel version has problems with the USB system. If I choose in GRUB an 
older kernel version (e.g. 5.0.0-37) everything is fine.
  Same problem with kernel 5.3.0-28.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Feb 16 05:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7817]
  InstallationDate: Installed on 2019-03-19 (333 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: MSI MS-7817
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  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/linux/+bug/1863455/+subscriptions

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


[Touch-packages] [Bug 1861081] Re: Dependency error installing pulseaudio-module-bluetooth

2020-02-16 Thread Daniel van Vugt
** Tags added: bionic

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

Title:
  Dependency error installing pulseaudio-module-bluetooth

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  running apt install pulseaudio-module-bluetooth i get the following error:
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   pulseaudio-module-bluetooth : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is to be installed
 Depends: pulseaudio (= 1:11.1-1ubuntu7.4)
  E: Unable to correct problems, you have held broken packages.

  seems likely related to: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622
  but with a different package

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

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


[Touch-packages] [Bug 1863186] Re: package sdl2-dev depends on outdated version of libpulse-dev

2020-02-16 Thread Daniel van Vugt
It seems this is a side effect of a mistake made in the release and
subsequent withdrawal of update 1:11.1-1ubuntu7.5. So it's not a bug in
the code but is a problem people will encounter with Ubuntu updates...

This should automatically correct itself with the re-release of
1:11.1-1ubuntu7.5. In the meantime you can manually install whichever
set of packages you need from either:

1:11.1-1ubuntu7.4:
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4/+build/17893827

1:11.1-1ubuntu7.5:
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.5/+build/18146190


** Tags added: bionic

** Tags added: update-reverted

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  package sdl2-dev depends on outdated version of libpulse-dev

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  $ sudo apt install libsdl2-dev 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libsdl2-dev : Depends: libpulse-dev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  $ sudo aptitude install libsdl2-dev 
  The following NEW packages will be installed:

  

   The following packages have unmet dependencies:
   libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is installed
  Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is installed

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-02-16 Thread Daniel van Vugt
** Tags added: focal

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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


[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

2020-02-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Confirmed
Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions

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


[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

2020-02-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: command-not-found (Ubuntu)
   Status: New => Confirmed

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Confirmed
Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions

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


[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

2020-02-16 Thread Daniel Llewellyn
** Tags added: champagne

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Confirmed
Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions

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


[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

2020-02-16 Thread Daniel Llewellyn
** Also affects: command-not-found (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Confirmed
Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions

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


[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

2020-02-16 Thread Neil McPhail
$ apt policy python3-commandnotfound 
python3-commandnotfound:
  Installed: 19.10.0
  Candidate: 19.10.0
  Version table:
 *** 19.10.0 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Confirmed
Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions

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


[Touch-packages] [Bug 1863532] [NEW] Invoking "python" brings inappropriate response from command-not-found when python3 installed

2020-02-16 Thread Neil McPhail
Public bug reported:

Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have
python 2.7 installed, but have python 3 installed as per default.

Please see ascii-cast at
https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

Running `python` brings up text from command-not-found which suggests
installing `python3` as a solution to the missing command. `python3` is
already installed, is a later version than the one indicated by command-
not-found and does not supply a binary or symlink named `python`.

$ apt policy python
python:
  Installed: (none)
  Candidate: (none)
  Version table:
 2.7.17-1 -1
100 /var/lib/dpkg/status
$ apt policy python3
python3:
  Installed: 3.8.0-3
  Candidate: 3.8.0-3
  Version table:
 *** 3.8.0-3 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
$ apt policy command-not-found
command-not-found:
  Installed: 19.10.0
  Candidate: 19.10.0
  Version table:
 *** 19.10.0 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status

I don't know whether this is a bug in python3 or command-not-found (the
latter of which doesn't seem to have been updated for 20.04 yet). i
don't know if it is intentional that `python3` will not provide a binary
or symlink named `python`. if that is the case, the output of `command-
not-found` should be updated to reflect that.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3 3.8.0-3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Feb 17 01:35:16 2020
InstallationDate: Installed on 2019-10-11 (128 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
SourcePackage: python3-defaults
UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

** Affects: command-not-found (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug champagne focal

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Confirmed
Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1862453] Re: static ip netplan does not apply on boot

2020-02-16 Thread David Parks
Attached is the output of 'journalctl -b --no-pager'.

After booting, 'ip a' confirmed no ip was assigned.  in the attached
journal, 'sudo netplan apply' was called at 17:58:22 and the network
came up within a couple of seconds.

** Attachment added: "Output of: 'journalctl -b --no-pager'"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862453/+attachment/5328770/+files/200216jrnl.txt

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

Title:
  static ip netplan does not apply on boot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was advised to report a bug when I posted the following thread...
  https://askubuntu.com/questions/1208145/netplan-apply-required-after-reboot

  After a reboot, I must manually run "sudo netplan apply" to set the
  static IP described in 50-cloud-init.yaml.

  Journalctl repeatedly reports:
Feb 04 20:10:52 lei systemd-networkd[935]: Failed to connect to bus: 
Permission denied
  during boot.

  Once booted, I can manually run "netplan apply" and everything
  configures normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.38
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Sat Feb  8 08:54:00 2020
  InstallationDate: Installed on 2019-12-28 (42 days ago)
  InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=cb6893b3-aa11-452c-8b50-cf43b1ddaee3 ro maybe-ubiquity
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: Z97 Anniversary
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd03/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Anniversary: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.

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

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


[Touch-packages] [Bug 1637355] Re: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2020-02-16 Thread Logan Rosen
*** This bug is a duplicate of bug 1621686 ***
https://bugs.launchpad.net/bugs/1621686

** This bug has been marked a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  I was uninstall python2 and reinstalled

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Oct 27 18:37:32 2016
  DuplicateSignature: package:python-gobject-2:2.28.6-12build1:el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-12-23 (309 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: Upgraded to trusty on 2016-10-19 (8 days ago)

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

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


[Touch-packages] [Bug 1632835] Re: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2020-02-16 Thread Logan Rosen
*** This bug is a duplicate of bug 1621686 ***
https://bugs.launchpad.net/bugs/1621686

** This bug has been marked a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade:
  sub-processo script post-installation instalado retornou estado de
  saída de erro 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  Referente ao python

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gobject-2 2.28.6-12ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 10 11:46:09 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2016-09-26 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1715857] Re: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 127

2020-02-16 Thread Logan Rosen
*** This bug is a duplicate of bug 1742024 ***
https://bugs.launchpad.net/bugs/1742024

** This bug has been marked a duplicate of bug 1742024
   package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127

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

Title:
  package python-gobject-2 2.28.6-12build1 failed to install/upgrade:
  子进程 已安装 post-installation 脚本 返回错误状态 127

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  package python-gobject-2 2.28.6-12build1 failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: python-gobject-2 2.28.6-12build1
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Fri Sep  8 19:38:39 2017
  DuplicateSignature: package:python-gobject-2:2.28.6-12build1:子进程 已安装 
post-installation 脚本 返回错误状态 127
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 127
  InstallationDate: Installed on 2016-11-17 (295 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu3
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
子进程 已安装 post-installation 脚本 返回错误状态 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1743727] Re: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

2020-02-16 Thread Logan Rosen
*** This bug is a duplicate of bug 1621686 ***
https://bugs.launchpad.net/bugs/1621686

** This bug has been marked a duplicate of bug 1621686
   package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

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

Title:
  package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade:
  子进程 已安装 post-installation 脚本 返回错误状态 1

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
  when pc powered up, the mistake appeared

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gobject-2 2.28.6-12ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Jan 12 15:09:31 2018
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2018-01-10 (7 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 
子进程 已安装 post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1742024] Re: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2020-02-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pygobject-2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in pygobject-2 package in Ubuntu:
  Confirmed

Bug description:
  any

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gobject-2 2.28.6-12ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Jan  9 02:12:11 2018
  DuplicateSignature:
   package:python-gobject-2:2.28.6-12ubuntu1
   Setting up python-cairo (1.8.8-2) ...
   /var/lib/dpkg/info/python-cairo.postinst: 6: 
/var/lib/dpkg/info/python-cairo.postinst: pycompile: not found
   dpkg: error processing package python-cairo (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2018-01-08 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: pygobject-2
  Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1508638] Re: Build with multiarch support

2020-02-16 Thread Logan Rosen
This was done in 2.28.6-12ubuntu1:
https://launchpad.net/ubuntu/+source/pygobject-2/2.28.6-12ubuntu1

** Changed in: pygobject-2 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Build with multiarch support

Status in pygobject-2 package in Ubuntu:
  Fix Released

Bug description:
  Build with multiarch support

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

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


[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines

2020-02-16 Thread Mathew Hodson
** Changed in: python-apt (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: python-apt (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Eoan:
  New

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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

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


[Touch-packages] [Bug 1860606] Re: TypeError: _fetch_archives() missing 1 required positional argument: 'allow_unauthenticated'

2020-02-16 Thread Mathew Hodson
** Tags added: regression-update

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

Title:
  TypeError: _fetch_archives() missing 1 required positional argument:
  'allow_unauthenticated'

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Disco:
  Fix Released
Status in python-apt source package in Eoan:
  Fix Released
Status in python-apt source package in Focal:
  Fix Released

Bug description:
  I was upgrading my workstation from 19.04 to 19.10 and following that
  to 20.04. In each case I used do-release-upgrade (without and with -d
  respectively). The 20.04 upgrade failed as the tool crashed on invalid
  function signature:

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-f_816ncr/focal", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeMain.py", line 
238, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 2082, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1998, in fullUpgrade
  if not self.doDistUpgradeFetching():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1233, in doDistUpgradeFetching
  self.cache._fetch_archives(self.fetcher, pm)
  TypeError: _fetch_archives() missing 1 required positional argument: 
'allow_unauthenticated'

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

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


[Touch-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication

2020-02-16 Thread Jan Dolezal
*** This bug is a duplicate of bug 1849859 ***
https://bugs.launchpad.net/bugs/1849859

The solution to this problem is here guys:
https://askubuntu.com/questions/1186081/xerox-workcentre-6015b-requires-
authentication-credentials-required-in-
order/1186501#1186501?newreg=b77db8f4e5e742de8a0b4092ad8acac0

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  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.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1849859] Re: smb printing fails

2020-02-16 Thread Jan Dolezal
This helped me to solve the same problem on my computer:
https://askubuntu.com/questions/1186081/xerox-workcentre-6015b-requires-
authentication-credentials-required-in-
order/1186501#1186501?newreg=b77db8f4e5e742de8a0b4092ad8acac0

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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


[Touch-packages] [Bug 1863518] Re: Menuitems with actions cannot be set sensitive when in popup menus (using Glade/Python)

2020-02-16 Thread Simon Lambourn
Glade file to go with the python file

** Attachment added: "Glade file to go with the python code"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1863518/+attachment/5328759/+files/menuitem_action_bug.glade

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

Title:
  Menuitems with actions cannot be set sensitive when in popup menus
  (using Glade/Python)

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The bug may be assigned to the wrong package: I'm using Glade 3.22.1
  and Python 3.7.5.

  Using popup menus, if I assign Gio.Actions to the menuitems, the menuitems 
become insensitive, so you cannot click on them, even if they have a handler 
for the "activate" signal as well.
  I can assign Gio.Actions successfully to menuitems in a menubar, or a 
drop_down menu attached to a menubar, or to other clickable widgets such as 
buttons, so I think the logic works.

  The Glade xml output looks as if it is correctly specified (although
  I'm no expert), so I guess that Gtk.Builder is not connecting the
  signals properly.   Or there might be a restriction that I'm not aware
  of... so apologies if I am trying to do something not supported, but I
  have tried to research this.

  Behaviour:  menuitems in popup menus that have actions assigned are
  always insensitive and cannot be made sensitive.

  Expected behaviour:   menuitems in popup menus that have actions
  assigned should be sensitive and activatable.

  I have attached the python and glade code which demonstrate the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgtk-3-0 3.24.12-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 16 20:37:22 2020
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (115 days ago)

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

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


[Touch-packages] [Bug 1863518] [NEW] Menuitems with actions cannot be set sensitive when in popup menus (using Glade/Python)

2020-02-16 Thread Simon Lambourn
Public bug reported:

The bug may be assigned to the wrong package: I'm using Glade 3.22.1 and
Python 3.7.5.

Using popup menus, if I assign Gio.Actions to the menuitems, the menuitems 
become insensitive, so you cannot click on them, even if they have a handler 
for the "activate" signal as well.
I can assign Gio.Actions successfully to menuitems in a menubar, or a drop_down 
menu attached to a menubar, or to other clickable widgets such as buttons, so I 
think the logic works.

The Glade xml output looks as if it is correctly specified (although I'm
no expert), so I guess that Gtk.Builder is not connecting the signals
properly.   Or there might be a restriction that I'm not aware of... so
apologies if I am trying to do something not supported, but I have tried
to research this.

Behaviour:  menuitems in popup menus that have actions assigned are
always insensitive and cannot be made sensitive.

Expected behaviour:   menuitems in popup menus that have actions
assigned should be sensitive and activatable.

I have attached the python and glade code which demonstrate the problem.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libgtk-3-0 3.24.12-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 16 20:37:22 2020
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to eoan on 2019-10-23 (115 days ago)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Python code to demonstrate the problem"
   
https://bugs.launchpad.net/bugs/1863518/+attachment/5328752/+files/menuitem_action_bug.py

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

Title:
  Menuitems with actions cannot be set sensitive when in popup menus
  (using Glade/Python)

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The bug may be assigned to the wrong package: I'm using Glade 3.22.1
  and Python 3.7.5.

  Using popup menus, if I assign Gio.Actions to the menuitems, the menuitems 
become insensitive, so you cannot click on them, even if they have a handler 
for the "activate" signal as well.
  I can assign Gio.Actions successfully to menuitems in a menubar, or a 
drop_down menu attached to a menubar, or to other clickable widgets such as 
buttons, so I think the logic works.

  The Glade xml output looks as if it is correctly specified (although
  I'm no expert), so I guess that Gtk.Builder is not connecting the
  signals properly.   Or there might be a restriction that I'm not aware
  of... so apologies if I am trying to do something not supported, but I
  have tried to research this.

  Behaviour:  menuitems in popup menus that have actions assigned are
  always insensitive and cannot be made sensitive.

  Expected behaviour:   menuitems in popup menus that have actions
  assigned should be sensitive and activatable.

  I have attached the python and glade code which demonstrate the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgtk-3-0 3.24.12-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 16 20:37:22 2020
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (115 days ago)

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

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


[Touch-packages] [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default

2020-02-16 Thread Mathew Hodson
** Tags added: packaging

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

Title:
  alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-
  conf to focal image by default

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
  alsa-lib, when we install the alsa-lib/libasound2, they are installed
  together with alsa-lib. But from 1.2.1 they are separated from the
  alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should
  install the ucm and topology too, otherwise those machines need ucm
  and topology will not work anymore, users have to install these two
  packages manually.

  Two packages we need to put into the focal image are:
  alsa-ucm-conf 1.2.1.2-2
  alsa-topology-conf 1.2.1-2

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

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


[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads

2020-02-16 Thread Jamie
Running into this issue on 19.10, so none of the unity-specific
solutions work. If I switch TTY with ctrl+alt+F1, after I try to log
back in and just see the desktop background, I'm brought to login screen
again, but this time log in is successful. Disabling all gnome
extensions doesn't seem to help. Happens every time after suspending
laptop.

Not sure if this is helpful or relevant, but I tried looking at the
following logs:

% journalctl -e /usr/bin/gnome-shell

Feb 16 12:15:05 tula-Z gnome-shell[2114]: JS WARNING: 
[resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to 
method Clutter.Actor.destroy: expected 0, got 
Feb 16 12:15:05 tula-Z gnome-shell[2114]: JS WARNING: 
[resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to 
method Clutter.Actor.destroy: expected 0, got 
Feb 16 12:15:15 tula-Z gnome-shell[2114]: An active wireless connection, in 
infrastructure mode, involves no access point?
Feb 16 12:15:15 tula-Z gnome-shell[2114]: An active wireless connection, in 
infrastructure mode, involves no access point?
Feb 16 12:15:26 tula-Z gnome-shell[8675]: Failed to obtain high priority context
Feb 16 12:15:26 tula-Z gnome-shell[8675]: Failed to obtain high priority context
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Unset XDG_SESSION_ID, 
getCurrentSessionProxy() called outside a user session. Asking logind directly.
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Will monitor session c3
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Getting invalid resource scale 
property
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_hello: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Error while sending AddMatch() 
message: The connection is closed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Getting invalid resource scale 
property
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_hello: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Error while sending AddMatch() 
message: The connection is closed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:28 tula-Z gnome-shell[8675]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Feb 16 12:15:28 tula-Z gnome-shell[8675]: JS WARNING: 
[resource:///org/gnome/shell/ui/windowManager.js 1640]: reference to undefined 
property "MetaWindowXwayland"
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:28 tula-Z gnome-shell[8675]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Feb 16 12:15:28 tula-Z gnome-shell[8675]: JS WARNING: 
[resource:///org/gnome/shell/ui/windowManager.js 1640]: reference to undefined 
property "MetaWindowXwayland"
Feb 16 12:15:28 tula-Z gnome-shell[8675]: Registering session with GDM
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.180/org/ayatana/NotificationItem/software_update_available
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.90/org/ayatana/NotificationItem/dropbox_client_2433
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon

Hope this is helpful!

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Triaged

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window 

[Touch-packages] [Bug 1060228]

2020-02-16 Thread marcec
The upstream bug was closed as invalid in 2016, with no activity since
then (i.e., no more "me too!"s), and I had switched to KDE4 about two
years before that, so haven't really cared about this bug in the last 6
years.  Hence: Is this bug still reproducible, or can it be closed now?
Because I don't know about you, but I'd be glad to get it off of my open
bug list ;-) .

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

Title:
  dm-tool lock + alt-ctrl-f7

Status in lightdm package in Ubuntu:
  Invalid
Status in Gentoo Linux:
  Unknown

Bug description:
  Ubuntu 12.04.1
  lightdm 1.2.1-0ubuntu1
  lightdm-gtk-greeter 1.1.5-0ubuntu1

  
  * Run...
  dm-tool lock
  Press alt-ctrl-f7

  Now I'm back in without a password.

  Same with switch-to-greeter

  
  I don't know if it's supposed to be this way or it's a security problem.

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

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


[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2020-02-16 Thread Dan Streetman
bionic verification:

root@lp1845909-b:# dpkg -l systemd|grep ii
ii  systemd237-3ubuntu10.38 amd64system and service manager
root@lp1845909-b:# ip -6 a show dev pppoe
3: pppoe@ens3:  mtu 1500 state UP qlen 
1000
inet6 fe80::5054:ff:fe88:4ba3/64 scope link 
   valid_lft forever preferred_lft forever


root@lp1845909-b:~# dpkg -l systemd|grep ii
ii  systemd237-3ubuntu10.39 amd64system and service manager
root@lp1845909-b:~# ip -6 a show dev pppoe
root@lp1845909-b:~# 


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

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

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  in some situations when a networkd interface is configured with
  LinkLocalAddressing=no, networkd still assigns a link-local address to
  it

  [test case]

  see comment 3.

  note I was only able to reproduce this at boot time; if the vlan
  interface is removed (i.e. 'sudo ip l del pppoe') and then networkd
  restarted, the pppoe interface is created and does not have a link-
  local address.  This is due to this bug being triggered by timing, as
  a vlan interface is raised by the kernel when its parent interface is
  raised, in this case by networkd itself.

  [regression potential]

  this changes how ipv6ll addresses are managed and dropped, as well as
  changing when foreign addresses are dropped (later in config process).
  Any regressions would likely be around incorrectly setting ipv6ll
  addresses, or complete failure to complete interface configuration.

  [scope]

  this is fixed upstream by:
  https://github.com/systemd/systemd/pull/13927

  and also requires the upstream PR referenced in the original description:
  upstream patch: https://github.com/systemd/systemd/pull/13565

  this is required for focal (uploaded already), eoan, and bionic.  It
  may be required for xenial.

  [other info]

  Note, the original description below is incorrect, the issue/patch it
  references is not enough to fix this issue.

  original description:

  --

  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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


[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2020-02-16 Thread Dan Streetman
eoan verification:

root@lp1845909-e:~# dpkg -l systemd|grep ii
ii  systemd242-7ubuntu3.6 amd64system and service manager
root@lp1845909-e:~# ip -6 a show pppoe
3: pppoe@ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
inet6 fe80::5054:ff:fe80:712e/64 scope link 
   valid_lft forever preferred_lft forever


root@lp1845909-e:~# dpkg -l systemd|grep ii
ii  systemd242-7ubuntu3.7 amd64system and service manager
root@lp1845909-e:~# ip -6 a show pppoe
root@lp1845909-e:~#

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

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  in some situations when a networkd interface is configured with
  LinkLocalAddressing=no, networkd still assigns a link-local address to
  it

  [test case]

  see comment 3.

  note I was only able to reproduce this at boot time; if the vlan
  interface is removed (i.e. 'sudo ip l del pppoe') and then networkd
  restarted, the pppoe interface is created and does not have a link-
  local address.  This is due to this bug being triggered by timing, as
  a vlan interface is raised by the kernel when its parent interface is
  raised, in this case by networkd itself.

  [regression potential]

  this changes how ipv6ll addresses are managed and dropped, as well as
  changing when foreign addresses are dropped (later in config process).
  Any regressions would likely be around incorrectly setting ipv6ll
  addresses, or complete failure to complete interface configuration.

  [scope]

  this is fixed upstream by:
  https://github.com/systemd/systemd/pull/13927

  and also requires the upstream PR referenced in the original description:
  upstream patch: https://github.com/systemd/systemd/pull/13565

  this is required for focal (uploaded already), eoan, and bionic.  It
  may be required for xenial.

  [other info]

  Note, the original description below is incorrect, the issue/patch it
  references is not enough to fix this issue.

  original description:

  --

  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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


[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart=

2020-02-16 Thread Dan Streetman
bionic verification:

root@lp1849261-b:~# dpkg -l systemd | grep ii
ii  systemd237-3ubuntu10.39 amd64system and service manager
root@lp1849261-b:~# systemctl status test failure
● test.service
   Loaded: loaded (/etc/systemd/system/test.service; static; vendor preset: enab
   Active: inactive (dead)

● failure.service
   Loaded: loaded (/etc/systemd/system/failure.service; static; vendor preset: e
   Active: inactive (dead)
root@lp1849261-b:~# systemctl start test
root@lp1849261-b:~# sleep 10 ; systemctl status test failure
● test.service
   Loaded: loaded (/etc/systemd/system/test.service; static; vendor preset: enab
   Active: active (running) since Sun 2020-02-16 14:42:27 UTC; 2s ago
 Main PID: 1338 (sh)
Tasks: 2 (limit: 4702)
   CGroup: /system.slice/test.service
   ├─1338 /bin/sh -c /bin/sleep 10; /bin/false
   └─1342 /bin/sleep 10

Feb 16 14:42:27 lp1849261-b systemd[1]: Started test.service.

● failure.service
   Loaded: loaded (/etc/systemd/system/failure.service; static; vendor preset: e
   Active: inactive (dead)
root@lp1849261-b:~# journalctl -b -u test --no-pager
-- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Sun 2020-02-16 14:43:08 
UTC. --
Feb 16 14:42:06 lp1849261-b systemd[1]: Started test.service.
Feb 16 14:42:16 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 16 14:42:16 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
Feb 16 14:42:16 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
Feb 16 14:42:16 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 1.
Feb 16 14:42:16 lp1849261-b systemd[1]: Stopped test.service.
Feb 16 14:42:16 lp1849261-b systemd[1]: Started test.service.
Feb 16 14:42:26 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 16 14:42:26 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
Feb 16 14:42:27 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
Feb 16 14:42:27 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 2.
Feb 16 14:42:27 lp1849261-b systemd[1]: Stopped test.service.
Feb 16 14:42:27 lp1849261-b systemd[1]: Started test.service.
Feb 16 14:42:37 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 16 14:42:37 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
Feb 16 14:42:37 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
Feb 16 14:42:37 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 3.
Feb 16 14:42:37 lp1849261-b systemd[1]: Stopped test.service.
Feb 16 14:42:37 lp1849261-b systemd[1]: Started test.service.
Feb 16 14:42:47 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 16 14:42:47 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
Feb 16 14:42:47 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
Feb 16 14:42:47 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 4.
Feb 16 14:42:47 lp1849261-b systemd[1]: Stopped test.service.
Feb 16 14:42:47 lp1849261-b systemd[1]: Started test.service.
Feb 16 14:42:57 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 16 14:42:57 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
Feb 16 14:42:57 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
Feb 16 14:42:57 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 5.
Feb 16 14:42:57 lp1849261-b systemd[1]: Stopped test.service.
Feb 16 14:42:57 lp1849261-b systemd[1]: Started test.service.
Feb 16 14:43:07 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 16 14:43:07 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
Feb 16 14:43:08 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
Feb 16 14:43:08 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 6.
Feb 16 14:43:08 lp1849261-b systemd[1]: Stopped test.service.
Feb 16 14:43:08 lp1849261-b systemd[1]: Started test.service.
root@lp1849261-b:~# journalctl -b -u failure --no-pager
-- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Sun 2020-02-16 14:43:18 
UTC. --
-- No entries --


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

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

Title:
  Update systemd for ubuntu 18.04 with fix for interaction between
  OnFailure= and Restart=

Status in Ubuntu on 

[Touch-packages] [Bug 1859862] Re: networkd doesn't re-enable ipv6 unless mtu is set

2020-02-16 Thread Dan Streetman
bionic verification:

root@lp1859862-b:~# dpkg -l systemd|grep ii
ii  systemd237-3ubuntu10.39 amd64system and service manager
root@lp1859862-b:~# cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6 
1
root@lp1859862-b:~# ip -6 a show dev ens3
root@lp1859862-b:~# systemctl restart systemd-networkd
root@lp1859862-b:~# ip -6 a show dev ens3
2: ens3:  mtu 1500 state UP qlen 1000
inet6 2001:db8::100/64 scope global 
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link 
   valid_lft forever preferred_lft forever
root@lp1859862-b:~# cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6 
0


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

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

Title:
  networkd doesn't re-enable ipv6 unless mtu is set

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  if the 'disable_ipv6' procfs setting is disabled, and networkd is
  configured with ipv6 networking, networkd will not enable ipv6 via the
  procfs setting unless the interface mtu is also set to a custom value,
  that doesn't match the current interface mtu.

  [test case]

  create networkd config similar to:

  [Match]
  MACAddress=52:54:00:0c:09:77
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=2001:db8::100/64

  manually disable ipv6 for the interface:

  ubuntu@lp1859862-b:~$ echo 1 | sudo tee 
/proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1

  the interface should not contain any ipv6 addresses:

  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  restart networkd; it should enable ipv6 as ipv6 addresses are
  configured, but it does not:

  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  Note that with the mtu set, it will successfully re-enable ipv6;
  modify the networkd config to set the mtu by adding this:

  [Link]
  MTUBytes=1400

  (be sure to set the MTU config to something other than its current
  mtu)

  verify ipv6 is still disabled and has no addresses, then restart and
  check again:

  ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
  0
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  2: ens3:  mtu 1400 state UP qlen 1000
  inet6 2001:db8::100/64 scope global
     valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe0c:977/64 scope link
     valid_lft forever preferred_lft forever

  That should be the behavior even if MTUBytes is not set.

  [regression potential]

  as this adjusts when the procfs 'disable_ipv6' setting is changed, the
  regression potential could cause failure to properly set/create ipv6
  addresses, or to leave ipv6 disabled entirely.

  [scope]

  This is needed in Bionic and Eoan.

  the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765
  which is included starting in v243, so it is included already in
  Focal.

  Ignoring Disco, as it is EOL next week.

  This problem was introduced by commit
  44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting
  in v239, but also backported to Bionic in bug 1850704.

  [other info]

  for Eoan, this bug has always existed since release, but for Bionic,
  this is a regression introduced by bug 1850704.  However, manual
  disabling of ipv6 is very unusual, so this bug is unlikely to have an
  impact to many systems.

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

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


[Touch-packages] [Bug 1859862] Re: networkd doesn't re-enable ipv6 unless mtu is set

2020-02-16 Thread Dan Streetman
** Description changed:

  [impact]
  
  if the 'disable_ipv6' procfs setting is disabled, and networkd is
  configured with ipv6 networking, networkd will not enable ipv6 via the
  procfs setting unless the interface mtu is also set to a custom value,
  that doesn't match the current interface mtu.
  
  [test case]
  
  create networkd config similar to:
  
  [Match]
  MACAddress=52:54:00:0c:09:77
  Name=ens3
  
  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=2001:db8::100/64
  
  manually disable ipv6 for the interface:
  
  ubuntu@lp1859862-b:~$ echo 1 | sudo tee 
/proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1
  
  the interface should not contain any ipv6 addresses:
  
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$
  
  restart networkd; it should enable ipv6 as ipv6 addresses are
  configured, but it does not:
  
  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$
  
  Note that with the mtu set, it will successfully re-enable ipv6; modify
  the networkd config to set the mtu by adding this:
  
  [Link]
  MTUBytes=1400
+ 
+ (be sure to set the MTU config to something other than its current mtu)
  
  verify ipv6 is still disabled and has no addresses, then restart and
  check again:
  
  ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
  0
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  2: ens3:  mtu 1400 state UP qlen 1000
  inet6 2001:db8::100/64 scope global
     valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe0c:977/64 scope link
     valid_lft forever preferred_lft forever
  
  That should be the behavior even if MTUBytes is not set.
  
  [regression potential]
  
  as this adjusts when the procfs 'disable_ipv6' setting is changed, the
  regression potential could cause failure to properly set/create ipv6
  addresses, or to leave ipv6 disabled entirely.
  
  [scope]
  
  This is needed in Bionic and Eoan.
  
  the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which
  is included starting in v243, so it is included already in Focal.
  
  Ignoring Disco, as it is EOL next week.
  
  This problem was introduced by commit
  44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in
  v239, but also backported to Bionic in bug 1850704.
  
  [other info]
  
  for Eoan, this bug has always existed since release, but for Bionic,
  this is a regression introduced by bug 1850704.  However, manual
  disabling of ipv6 is very unusual, so this bug is unlikely to have an
  impact to many systems.

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

Title:
  networkd doesn't re-enable ipv6 unless mtu is set

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  if the 'disable_ipv6' procfs setting is disabled, and networkd is
  configured with ipv6 networking, networkd will not enable ipv6 via the
  procfs setting unless the interface mtu is also set to a custom value,
  that doesn't match the current interface mtu.

  [test case]

  create networkd config similar to:

  [Match]
  MACAddress=52:54:00:0c:09:77
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=2001:db8::100/64

  manually disable ipv6 for the interface:

  ubuntu@lp1859862-b:~$ echo 1 | sudo tee 
/proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1

  the interface should not contain any ipv6 addresses:

  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  restart networkd; it should enable ipv6 as ipv6 addresses are
  configured, but it does not:

  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  Note that with the mtu set, it will successfully re-enable ipv6;
  modify the networkd config to set the mtu by adding this:

  [Link]
  MTUBytes=1400

  (be sure to set the MTU config to something other than its current
  mtu)

  verify ipv6 is still disabled and has no addresses, then restart and
  check again:

  ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
  0
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  2: ens3:  mtu 1400 state UP qlen 1000
  inet6 2001:db8::100/64 scope global
     valid_lft forever preferred_lft forever
  inet6 

[Touch-packages] [Bug 1836695] Re: systemd fails to setup static routes at boot when using DHCP

2020-02-16 Thread Dan Streetman
verified on bionic

ubuntu@lp1836695-b:~$ dpkg -l systemd|grep ii
ii  systemd237-3ubuntu10.39 amd64system and service manager
ubuntu@lp1836695-b:~$ ip r
10.0.0.0/8 via 192.168.122.1 dev ens3 proto static 
192.168.122.0/24 dev ens3 proto kernel scope link src 192.168.122.35 


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

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

Title:
  systemd fails to setup static routes at boot when using DHCP

Status in netplan:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  a systemd-networkd configuration that uses ipv4 dhcp but ignores the
  dhcp-provided route, and instead sets up a static route, and also does
  not include a static ipv4 address, fails to actually create the static
  route.

  This is due to networkd attempting to set up the static route before
  the dhcp ipv4 address is assigned, and the kernel does not allow
  creation of the route before setting up corresponding ipv4 address.

  this results in a network that does have the dhcp-provided ipv4
  address, but is missing both its dhcp-provided route (because networkd
  is configured to ignore it) and the static route (because networkd was
  not able to create it).

  [test case]

  (remove or unconfigure netplan, so it will not conflict with this
  manual networkd configuration)

  create a networkd config file, e.g.:

  $ cat /etc/systemd/network/10-eth0.network 
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [Route]
  Destination=10.0.0.0/8
  Gateway=10.202.51.1

  [DHCP]
  UseRoutes=false

  
  then *reboot* the system, and check that the static route was not applied:

  $ ip r
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 

  
  note that because networkd does not remove ipv4 addresses that it manages 
(including dhcpv4 addresses), restarting networkd after the initial boot
  will correctly create the static route, e.g.:

  ubuntu@lp1836695-b:~$ ip r
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 
  ubuntu@lp1836695-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1836695-b:~$ ip r
  10.0.0.0/8 via 10.202.51.1 dev eth0 proto static 
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 

  [regression potential]

  adjusting how networkd works always carries the risk of breaking
  networking.

  TBD detailed regression potential after analyzing fix.

  [other info]

  original description:

  --

  
  Consider the following setup:

  network:
    version: 2
    renderer: networkd
    ethernets:
  ens4:
    dhcp-identifier: mac
    dhcp4: yes
    dhcp4-overrides:
  use-dns: no
  use-ntp: no
  send-hostname: no
  use-hostname: no
  use-routes: no
    routes:
    - to: 10.0.0.0/8
  via: 10.50.0.1
    optional: true

  Thus I only need to get the IP address by DHCP, then add some static
  routes. This setup doesn't work. Apparently `routes` keyword only
  works when using static addresses.

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

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


[Touch-packages] [Bug 1703821] Re: Dovecot and Apparmor complains at operation file_inherit

2020-02-16 Thread Christian Boltz
For the records: Upstream commit
a57f01d86bdb01647966f3eeff7a1cc3fc6abd76 (from 2019-02-10) added rules
to allow this (with an additional type=stream restriction, which matches
the log mentioned in this bugreport), and was also backported to the
maintenance branches.


Therefore I'll mark the AppArmor part as "fix released".

** Changed in: apparmor
   Status: Expired => Fix Released

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

Title:
  Dovecot and Apparmor complains at operation file_inherit

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Expired
Status in dovecot package in Ubuntu:
  Invalid

Bug description:
  My server is running Ubuntu 17.04 and Dovecot 2.2.27 (c0f36b0).
  Apparmor is still complaining about problems with file_inherit. I have
  put the profiles in complain-only mode, so I can continue, but still,
  it's a problem.

  Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400
  audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/sbin/dovecot"

  Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400
  audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/lib/dovecot/anvil"

  My configuration of Dovecot has changed slightly:

  /etc/dovecot/dovecot-sql.conf.ext
 driver = mysql
 connect = host=localhost dbname=mail user=mail password=mailpassword
 default_pass_scheme = MD5-CRYPT
 password_query = ...
 user_query = ...

  /etc/dovecot/conf.d/10-auth.conf
 disable_plaintext_auth = yes
 auth_mechanisms = plain login
 #!include auth-system.conf.ext
 !include auth-sql.conf.ext

  /etc/dovecot/conf.d/10-mail.conf
 mail_location = maildir:/var/vmail/%d/%n
 mail_uid = vmail
 mail_gid = mail
 first_valid_uid = 150
 last_valid_uid = 150

  /etc/dovecot/conf.d/10-ssl.conf
 ssl = required
 ssl_cert = 

  /usr/sbin/dovecot flags=(complain,attach_disconnected) {
#include 
#include 
#include 
#include 
#include 
#include 
#include 

capability chown,
capability dac_override,
capability fsetid,
capability kill,
capability net_bind_service,
capability setuid,
capability sys_chroot,
capability sys_resource,

/etc/dovecot/** r,
/etc/mtab r,
/etc/lsb-release r,
/etc/SuSE-release r,
@{PROC}/@{pid}/mounts r,
/usr/bin/doveconf rix,
/usr/lib/dovecot/anvil Px,
/usr/lib/dovecot/auth Px,
/usr/lib/dovecot/config Px,
/usr/lib/dovecot/dict Px,
/usr/lib/dovecot/dovecot-auth Pxmr,
/usr/lib/dovecot/imap Pxmr,
/usr/lib/dovecot/imap-login Pxmr,
/usr/lib/dovecot/lmtp Px,
/usr/lib/dovecot/log Px,
/usr/lib/dovecot/managesieve Px,
/usr/lib/dovecot/managesieve-login Pxmr,
/usr/lib/dovecot/pop3 Px,
/usr/lib/dovecot/pop3-login Pxmr,
/usr/lib/dovecot/ssl-build-param rix,
/usr/lib/dovecot/ssl-params Px,
/usr/sbin/dovecot mrix,
/usr/share/dovecot/protocols.d/   r,
/usr/share/dovecot/protocols.d/** r,
/var/lib/dovecot/ w,
/var/lib/dovecot/* rwkl,
/var/spool/postfix/private/auth w,
/var/spool/postfix/private/dovecot-lmtp w,
/{,var/}run/dovecot/ rw,
/{,var/}run/dovecot/** rw,
link /{,var/}run/dovecot/** -> /var/lib/dovecot/**,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

  Profile usr.lib.dovecot.anvil:

  #include 

  /usr/lib/dovecot/anvil flags=(complain) {
#include 
#include 

capability setuid,
capability sys_chroot,

/usr/lib/dovecot/anvil mr,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

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

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


[Touch-packages] [Bug 1831459] Re: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it

2020-02-16 Thread Dan Streetman
storage test passes.

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

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

Title:
  'storage' test needs to wait for systemd-cryptsetup to be active
  before stopping it

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  test case fails because it does not wait for the service to become
  active before stopping it, resulting in failure to rmmod the
  scsi_debug module because it's still in use.

  [test case]

  check 'storage' test results for systemd in autopkgtest logs, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz

  [regression potential]

  low; test case fix only.

  [other info]

  detected and reported by @cascardo in bug 1814373 comment 4 and 5, but
  separate (non-test) systemd bugfix uploaded for that bug so opening
  this bug to track fixing the test case.

  larger fixes/improvements to 'storage' testcase in bug 1829347, but
  those rejected.

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

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


[Touch-packages] [Bug 1863455] Re: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28

2020-02-16 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/1863455

Title:
  USB system (mouse and keybord) are not working since kernel update to
  5.3.0-26 and 5.3.0-28

Status in xorg package in Ubuntu:
  New

Bug description:
  Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. 
Keyboard and mouse (both connected via USB) are not working. It looks like 
everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the 
new kernel version has problems with the USB system. If I choose in GRUB an 
older kernel version (e.g. 5.0.0-37) everything is fine.
  Same problem with kernel 5.3.0-28.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Feb 16 05:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7817]
  InstallationDate: Installed on 2019-03-19 (333 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: MSI MS-7817
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  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/1863455/+subscriptions

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


[Touch-packages] [Bug 1863447] Re: openssh outdated by 8.2

2020-02-16 Thread Hans Joachim Desserud
** Tags added: upgrade-software-version

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

Title:
  openssh outdated by 8.2

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi,

  yeah, it's not yet a bug, but it will become a (security) bug within
  lifetime of 20.04 if not 'fixed'.

  Currently openssh for Ubuntu 20.04 is still on 8.1p1, while upstream
  the version 8.2 has just been released:

  https://lists.mindrot.org/pipermail/openssh-unix-
  announce/2020-February/000138.html

  It comes with important security updates, e.g. not accepting SHA-1 for
  key generation/signature anymore, and using FIDO2/U2F-tokens as a
  second factor. Especially the latter significantly improves security
  and helps against stealing keys and hijacking machines.

  It would be important (and nice) to have these improvements of
  security in Ubuntu 20.04.

  
  It might not yet be seen as a security vulnerability, but it will probably 
become one soon. 

  Thanks

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

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


[Touch-packages] [Bug 1863455] [NEW] USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28

2020-02-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. Keyboard 
and mouse (both connected via USB) are not working. It looks like everything is 
frozen, but also ALT+PRINT REISUB is not working, so I guess the new kernel 
version has problems with the USB system. If I choose in GRUB an older kernel 
version (e.g. 5.0.0-37) everything is fine.
Same problem with kernel 5.3.0-28.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sun Feb 16 05:14:11 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed
 virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed
 virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller [1462:7817]
InstallationDate: Installed on 2019-03-19 (333 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
MachineType: MSI MS-7817
ProcEnviron:
 LANGUAGE=de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V4.1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-P33 (MS-7817)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7817
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
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 fonts kubuntu ubuntu
-- 
USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 
and 5.3.0-28
https://bugs.launchpad.net/bugs/1863455
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