[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[Malte Deiseroth]

Given that a restart of the application is helping and fixes this
temporarily. This reminds be of a known issue in rygel, where disable
IGMP snooping is the solution if network bridges are involved and rygel
can only be discovered after a restart.
https://wiki.gnome.org/Projects/Rygel/FAQ

Not saying that this would help anything here. I just want to raise
awareness that this might also be caused by other external factors along
the network.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1881780).
https://bugs.launchpad.net/bugs/1828107

Title:
  gvfs can't list shares from smb servers that disabled SMB1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1949575] Re: Upgrade to 0.104 to at least fix memory leak in clamdscan

[Malte Kuhn]

0.103.5 is now distributed, containing the memleak fix above.
Basically this issue can be closed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949575

Title:
  Upgrade to 0.104 to at least fix memory leak in clamdscan

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951685] Re: Chromium flatpak reliably crashes xdg-desktop-portal

[Malte S. Stretz]

This is indeed fixed at least in version 1.8.1-1~flatpak1~20.04 as
installed from the official PPA.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951685

Title:
  Chromium flatpak reliably crashes xdg-desktop-portal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1951685/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951685] [NEW] Chromium flatpak reliably crashes xdg-desktop-portal

[Malte S. Stretz]

Public bug reported:

For a while now I am facing the issue that Chromium installed via
Flatpak after a minute or so stops working with a puzzling error
ERR_NO_SUPPORTED_PROXIES.  I guess this is due to the Proxy feature of
the desktop portal because now I noticed that the portal is actually
crashing shortly after I started Chromium and/or started browsing.

According to the stack trace this happens in get_one_app_state so I
think this bug was fixed in version 1.7.0 with this patch:
https://github.com/flatpak/xdg-desktop-
portal/commit/a0b641f1230016e8ed9a291c70d4dd226429dda4

Could that fix please be backported to 1.6.0/focal?

   PID: 15467 (xdg-desktop-por)
   UID: 1000 (xxx)
   GID: 1000 (xxx)
Signal: 11 (SEGV)
 Timestamp: Sat 2021-11-20 16:55:00 CET (4min 23s ago)
  Command Line: /usr/libexec/xdg-desktop-portal
Executable: /usr/libexec/xdg-desktop-portal
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/xdg-desktop-portal.service
  Unit: user@1000.service
 User Unit: xdg-desktop-portal.service
 Slice: user-1000.slice
 Owner UID: 1000 (xxx)
   Boot ID: 1841d625a5354885a778e18a20b48103
Machine ID: 30e0f491ec7847428bc900251dc271af
  Hostname: xxx
   Storage: 
/var/lib/systemd/coredump/core.xdg-desktop-por.1000.1841d625a5354885a778e18a20b48103.15467.1637423700.lz4
   Message: Process 15467 (xdg-desktop-por) of user 1000 dumped core.

Stack trace of thread 15505:
#0  0x7f5990c485f4 g_str_hash (libglib-2.0.so.0 + 0x405f4)
#1  0x7f5990c4773c g_hash_table_lookup (libglib-2.0.so.0 + 
0x3f73c)
#2  0x5646137cf282 get_one_app_state (xdg-desktop-portal + 
0x30282)
#3  0x5646137cf778 background_monitor (xdg-desktop-portal + 
0x30778)
#4  0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5  0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609)
#6  0x7f5990b15293 __clone (libc.so.6 + 0x122293)

Stack trace of thread 15470:
#0  0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff)
#1  0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e)
#2  0x7f5990c5a4a3 g_main_context_iteration 
(libglib-2.0.so.0 + 0x524a3)
#3  0x7f5990c5a4f1 n/a (libglib-2.0.so.0 + 0x524f1)
#4  0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5  0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609)
#6  0x7f5990b15293 __clone (libc.so.6 + 0x122293)

Stack trace of thread 15475:
#0  0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff)
#1  0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e)
#2  0x7f5990c5a4a3 g_main_context_iteration 
(libglib-2.0.so.0 + 0x524a3)
#3  0x7f598e5f099d n/a (libdconfsettings.so + 0xa99d)
#4  0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5  0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609)
#6  0x7f5990b15293 __clone (libc.so.6 + 0x122293)

Stack trace of thread 15467:
#0  0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff)
#1  0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e)
#2  0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 
0x526f3)
#3  0x5646137bb7e8 main (xdg-desktop-portal + 0x1c7e8)
#4  0x7f5990a1a0b3 __libc_start_main (libc.so.6 + 0x270b3)
#5  0x5646137bb94e _start (xdg-desktop-portal + 0x1c94e)

Stack trace of thread 15471:
#0  0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff)
#1  0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e)
#2  0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 
0x526f3)
#3  0x7f5990eaff8a n/a (libgio-2.0.so.0 + 0x11ef8a)
#4  0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5  0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609)
#6  0x7f5990b15293 __clone (libc.so.6 + 0x122293)


xdg-desktop-portal:
  Installed: 1.6.0-1
  Candidate: 1.6.0-1
  Version table:
 *** 1.6.0-1 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status


Distributor ID: Neon
Description:KDE neon User - Plasma 25th Anniversary Edition
Release:20.04
Codename:   focal

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951685

Title:

[Bug 1949575] Re: Upgrade to 0.104 to at least fix memory leak in clamdscan

[Malte Kuhn]

Looks like it was backported to 0.103.4 https://github.com/Cisco-
Talos/clamav/pull/203

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949575

Title:
  Upgrade to 0.104 to at least fix memory leak in clamdscan

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1949575] Re: Upgrade to 0.104 to at least fix memory leak in clamdscan

[Malte Kuhn]

updated desc

** Description changed:

  clamav 0.104 is released.
  
  Containing a fix for a bigger memleak of clamdscan.
  
https://github.com/Cisco-Talos/clamav/commit/8fd1c66d9954aaed5019fafdcfd170b98882a2fe
+ 
+ Bug characteristic with massif (valgrind) confirmation
+ 
https://discord.com/channels/63602074370595/636275790660501523/857472324148265021
+ 
+ Fix:
+ https://github.com/Cisco-Talos/clamav/pull/181

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949575

Title:
  Upgrade to 0.104 to at least fix memory leak in clamdscan

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1949575] Re: Upgrade to 0.104 to at least fix memory leak in clamdscan

[Malte Kuhn]

** Description changed:

  clamav 0.104 is released.
  
  Containing a fix for a bigger memleak of clamdscan.
+ 
https://github.com/Cisco-Talos/clamav/commit/8fd1c66d9954aaed5019fafdcfd170b98882a2fe

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949575

Title:
  Upgrade to 0.104 to at least fix memory leak in clamdscan

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1949575] [NEW] Upgrade to 0.104 to at least fix memory leak in clamdscan

[Malte Kuhn]

Public bug reported:

clamav 0.104 is released.

Containing a fix for a bigger memleak of clamdscan.
https://github.com/Cisco-Talos/clamav/commit/8fd1c66d9954aaed5019fafdcfd170b98882a2fe

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


** Tags: upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949575

Title:
  Upgrade to 0.104 to at least fix memory leak in clamdscan

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921593] Re: do-release-upgrade fails with no error

[Malte Jan Kaffenberger]

Thank you for the hints, Brian!

There are some things I noticed which may have lead to the error:

- I had packages installed from 20.04 already
- packages from bionic were pinned to lower priority

The upgrade succeeded after removing the pin.

This issue can be closed I guess.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921593

Title:
  do-release-upgrade fails with no error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867502] Re: Netboot Loading libc6-udeb failed for unknown reasons (focal)

[Malte Schmidt]

Can confirm, rolled back my repository from one week ago, worked fine
back then.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867502

Title:
  Netboot Loading libc6-udeb failed for unknown reasons (focal)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863697] Re: not compatible with python3.8 on focal

[Malte Schmidt]

Affected, too. When can we expect the patch?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863697

Title:
  not compatible with python3.8 on focal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919468] Re: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD-method requests

[Malte Schmidt]

Hello Seth,

unfortunately, this is incorrect.

   HTTP/1.1 defines the "close" connection option for the sender to
   signal that the connection will be closed after completion of the
   response.

https://tools.ietf.org/html/rfc2616#section-14.10

But the server with Ubuntus HAProxy 2.0.13 will not proactively do it.
Therefore, as described above, it is very easy for a malicious
application to fill up the servers memory and connection pool.

With my minimal working example and a HAProxy docker container, you may
easily and rather quickly be able to reproduce that. If this is expected
behaviour, then I'm sorry for this ticket, which can be closed.
(Migrated all my HAProxy based endpoints to a version not having this
problem ;) )

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919468

Title:
  HAProxy 2.0.13 does not close connection even though "connection:
  close" is sent, leaves many connections in CLOSE-WAIT state for HEAD-
  method requests

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919468] Re: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD-method requests

[Malte Schmidt]

This was created 20 days ago. When can I expect somebody to look into
it?

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919468

Title:
  HAProxy 2.0.13 does not close connection even though "connection:
  close" is sent, leaves many connections in CLOSE-WAIT state for HEAD-
  method requests

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921593] [NEW] do-release-upgrade fails with no error

[Malte Jan Kaffenberger]

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.42
ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
Uname: Linux 4.15.0-139-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
Date: Sat Mar 27 19:10:01 2021
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-03-27 (0 days ago)

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


** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921593

Title:
  do-release-upgrade fails with no error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902371] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1

[Malte Jan Kaffenberger]

This is a VM.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902371

Title:
  package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd
  package pre-installation script subprocess returned error exit status
  1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902371] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1

[Malte Jan Kaffenberger]

Public bug reported:

happened while do-release-upgrade.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lxd 3.0.3-0ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Oct 31 14:56:38 2020
ErrorMessage: new lxd package pre-installation script subprocess returned error 
exit status 1
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: lxd
Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd 
package pre-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-10-31 (0 days ago)

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


** Tags: amd64 apport-package focal third-party-packages uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902371

Title:
  package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd
  package pre-installation script subprocess returned error exit status
  1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.

[Malte Deiseroth]

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

I guess this is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107

** This bug has been marked a duplicate of bug 1828107
   gvfs can't list shares from smb servers that disabled SMB1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1881780

Title:
  Nautilus requires SMBv1 to work from "Other Locations" without
  manually typing in the address.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[Malte Deiseroth]

This Bug is embarrassing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107

Title:
  gvfs can't list shares from smb servers that disabled SMB1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1898456] [NEW] hp-plugin downloads plugins via insecure HTTP

[Malte S. Stretz]

Public bug reported:

While looking what hp-plugin was doing when it was semmingly hung I
noticed that it calls wget to download an executable via plain HTTP even
though www.openprinting.org supports HTTPS:

Relevant part from ps axf:

 10353 pts/4Ss 0:00  |   \_ /bin/bash
 10492 pts/4Sl+0:07  |   |   \_ /usr/bin/python3 /usr/bin/hp-plugin
 10507 pts/5Ss+0:00  |   |   \_ /usr/bin/wget --cache=off -P 
$HOME/.hplip 
http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.20.3-plugin.run


Looks like there are two issues here:

1. Unless a local file exists, a plugin descriptor is downloaded from 
http://hplip.sf.net/plugin.conf
2. That one then contains the actual download URLs at www.openprinting.org 
which are plain HTTP as well

The first one has checksums so theoretically it might be ok to download
the latter via HTTP (though there is no reason to do so) but the
checksums are downloaded via plain HTTP as well.

** Affects: hplip
 Importance: Undecided
 Status: New

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

** Summary changed:

- hp-plugin downloads from openprinting.org via insecure HTTP from
+ hp-plugin downloads plugins via insecure HTTP

** Also affects: hplip
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898456

Title:
  hp-plugin downloads plugins via insecure HTTP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895821] [NEW] No voice typing with chromium snap at google docs

[Malte Deiseroth]

Public bug reported:

The voice typing feature of google docs is a online speech-to-text
converter. It can be found on any google docs document under Toosl>Voice
Typing and it only runs with Chrome or Chromium.

However while I can use this feature using the google chromium.deb
build. I cdoesn't work on the chromium snap. Instead the browser
constantly opens and closes the access to the microphone, resulting in a
flickering microphone icon in the top right of the screen.

The fact that this works with the .deb but not with the snap make me
think it is a snap related issue.


$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

$ apt-cache policy chromium-browser
chromium-browser:
  Installed: (none)
  Candidate: 1:85.0.4183.83-0ubuntu0.20.04.1
  Version table:
 1:85.0.4183.83-0ubuntu0.20.04.1 500
500 http://de.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
 80.0.3987.163-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

$ apt-cache policy google-chrome-stable 
google-chrome-stable:
  Installed: 85.0.4183.102-1
  Candidate: 85.0.4183.102-1
  Version table:
 *** 85.0.4183.102-1 100
100 /var/lib/dpkg/status

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: snap

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895821

Title:
  No voice typing with chromium snap at google docs

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893771] [NEW] gnome fonts too large / detected screen size incorrect

[Malte Kleemeier]

Public bug reported:

Hi!

after the latest update, I observe problems with the font size used by gdm and 
the gnome gui.
It seems that the font size is now twice as large as before. This affects the 
login screen as well as elements of the gui (top bar, icon names on the 
desktop, pop up menus when right-clicking on the desktop). Fonts of standard 
applications (firefox, libreofffice, etc.) still have the correct size.

I'm currently using a 43" 4K monitor. xpdyinfo correctly detects its
resolution (3840x2160), but the detected screen size is obviously wrong
(602x341 mm2, which would correspond to a 27" monitor).

Please see attached screenshot.

My NVidia Driver Version is: 440.100

The problem can be temporarily fixed by going to Settings->Displays, and
then clicking "Scale 200%" and "Apply". A dialog appears and asks
whether I would like to keep the setting. If I click "revert", all font
sizes are now ok. Unfortunately the problem reappears after a reboot.

Similar reports can be found under:
https://askubuntu.com/questions/1268993/ubuntu-20-04-font-and-ui-elements-too-big-on-login

Many thanks for your time!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  1 12:58:47 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev 
a1) (prog-if 00 [VGA controller])
InstallationDate: Installed on 2020-04-26 (127 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=6643d18b-001d-4ec7-a81b-e9b6f17236aa ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0701
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970 PRO GAMING/AURA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr0701:bd05/16/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rn970PROGAMING/AURA:rvrRev1.xx: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: SKU
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal fonts ubuntu

** Attachment added: "screen.jpg"
   https://bugs.launchpad.net/bugs/1893771/+attachment/5406456/+files/screen.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893771

Title:
  gnome fonts too large / detected screen size incorrect

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890535] [NEW] Parsing of /etc/gshadow can return bad pointers causing segfaults in applications

[Malte Schmidt]

Public bug reported:

This bug is already solved upstream
(https://sourceware.org/bugzilla/show_bug.cgi?id=20338) in 2.32 and has
to be backported.

It indirectly causes systemd-sysusers on 20.04/focal to fail
(https://github.com/systemd/systemd/issues/6512).

** Affects: glibc
 Importance: Unknown
 Status: Unknown

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


** Tags: glibc gshadow systemd-sysusers

** Bug watch added: Sourceware.org Bugzilla #20338
   https://sourceware.org/bugzilla/show_bug.cgi?id=20338

** Also affects: glibc via
   https://sourceware.org/bugzilla/show_bug.cgi?id=20338
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890535

Title:
  Parsing of /etc/gshadow can return bad pointers causing segfaults in
  applications

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1883234] Re: unix extensions not working?

[Malte Kleemeier]

I see, it's work in progress. Many thanks!

On 12.06.20 15:22, Andreas Hasenack wrote:
> It's messy, and I don't think there is a general case that works for
> everyone. The good news is that unix extensions for SMB3 are coming, and
> there are test implementations out there already.
>
> There was a talk about it in the recent samba XP 2020 conference, take a
> look at https://sambaxp.org/archive/
>
> day 3, track 2: "Optimizing Linux Access to Samba: POSIX Protocol
> Extensions for SMB3.1.1"
>
> The slides and video of the talk should be up soon.
>
> I'll close this bug in the meantime then.
>
>
> ** Changed in: samba (Ubuntu)
>Status: Incomplete => Invalid
>

-- 
Malte Kleemeier
Freudenbergstr. 13
28213 Bremen
Telefon:  +49 421 3971382
Mobil:+49 1575 3054600
 (+49 1575 8868309)
 (+49 179 1332707)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883234

Title:
  unix extensions not working?

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1883234] Re: unix extensions not working?

[Malte Kleemeier]

Hello Andreas,Many thanks for the fast reply!I also had to set "client min 
protocol = NT1" and to start smbclient with "-m NT1", but it actually works 
exactly  the way you said. I would never have found the solution without your 
kind  help. Again, many thanks!!Maybe the fact that unix extensions are coupled 
to the protocol level should be mentioned in the samba documentation (man page 
of smb.conf). I did a fair amount of research on the net and could not find any 
hint about that.One last question: Is it possible to share files with correct 
file permissions under the current SMB3 protocol? I know the SMB protocol comes 
from the windows realm, but I think it is not completely unreasonable to use it 
to share files between linux boxes.Regards,Malte Kleemeier
 Ursprüngliche Nachricht Von: Andreas Hasenack 
<1883...@bugs.launchpad.net> Datum: 12.06.20  14:15  (GMT+01:00) An: 
malte.kleeme...@googlemail.com Betreff: [Bug 1883234] Re: unix extensions not 
working? Unix extensions only work for the SMB1 protocol, which has 
beendeprecated and is no longer used by default. Development is ongoing 
tosupport them in SMB3.You can re-enable SMB1 by adding this to [global] in the 
server'ssmb.conf:server min protocol = NT1Can you please try again with the 
above setting and report back?** Changed in: samba (Ubuntu)   Status: New 
=> Incomplete-- You received this bug notification because you are subscribed 
to the bugreport.https://bugs.launchpad.net/bugs/1883234Title:  unix extensions 
not working?Status in samba package in Ubuntu:  IncompleteBug description:  I 
was trying to share home directories between two linux machines, so  I set-up a 
samba server (using the default the smb.conf, just  uncommenting things in the 
[homes] section, see attached smb.conf).  That worked nicely, except for one 
thing:  When mounting the shared home directory all files are marked as  
executable.  If is obviously due to the fact that unix permissions are not  
correctly send from server to client.  smbclient reports the following error:   
  smbclient //server/user Enter WORKGROUP\users's password:  Try "help" 
to get a list of possible commands. smb: \> stat testparm_v.log  Server 
doesn't support UNIX CIFS calls.     According to the samba docu support for 
unix permissions is controlled  by "unix extensions" in the [global] section of 
smb.conf. If no value  is supplied is is turned on by default. As can been been 
from the  output of "testparm -v" ("unix extensions = Yes") that unix 
extensions  are indeed enabled for my set-up.  So the expected behaviour is 
that file permissions are correctly  exported from the server when mounting the 
homes share.  Maybe I misunderstood something (samba configuration is quite  
complex), but I think I found an error in the samba package. Any  advice is 
welcome. Many thanks in advance!  Additional Information  1) Description:  
Ubuntu 20.04 LTS Release:   20.04  2) samba: Installed: 
2:4.11.6+dfsg-0ubuntu1.2To manage notifications about this bug go 
to:https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1883234/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883234

Title:
  unix extensions not working?

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1883234] [NEW] unix extensions not working?

[Malte Kleemeier]

Public bug reported:

I was trying to share home directories between two linux machines, so I
set-up a samba server (using the default the smb.conf, just uncommenting
things in the [homes] section, see attached smb.conf).

That worked nicely, except for one thing:

When mounting the shared home directory all files are marked as
executable.

If is obviously due to the fact that unix permissions are not correctly
send from server to client.

smbclient reports the following error:
   smbclient //server/user
   Enter WORKGROUP\users's password: 
   Try "help" to get a list of possible commands.
   smb: \> stat testparm_v.log 
   Server doesn't support UNIX CIFS calls.   

According to the samba docu support for unix permissions is controlled
by "unix extensions" in the [global] section of smb.conf. If no value is
supplied is is turned on by default. As can been been from the output of
"testparm -v" ("unix extensions = Yes") that unix extensions are indeed
enabled for my set-up.

So the expected behaviour is that file permissions are correctly
exported from the server when mounting the homes share.

Maybe I misunderstood something (samba configuration is quite complex),
but I think I found an error in the samba package. Any advice is
welcome. Many thanks in advance!

Additional Information

1) Description: Ubuntu 20.04 LTS
   Release: 20.04

2) samba:
   Installed: 2:4.11.6+dfsg-0ubuntu1.2

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

** Attachment added: "attachment.tgz"
   
https://bugs.launchpad.net/bugs/1883234/+attachment/5383199/+files/attachment.tgz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883234

Title:
  unix extensions not working?

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

Mainboard firmware update worked. Installable and bootable in both
legacy and uefi mode.

** Changed in: subiquity
   Status: New => Fix Released

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

** Changed in: curtin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

Sorry for the delay. Installation continues and finishes in UEFI mode.

Now we ran into boot issues (SSD is the same model, but mainboard
isn't), but those are unlikely Software related (seems like an AHCI
Driver bug in the mainboard firmware) - so we can't confirm that the
installed OS boots.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

So this issue can be closed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

[Malte Schmidt]

This was fixed for me by patching the latest firmware on the GBICs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

We'll try next week. Then i've physical access

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

As soon those patches are in the daily live iso - we would like to test
again. Please send us a notice, so we can report back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

After you mentioned UEFI, we are now able to install in bios legacy mode. 
ヽ(•‿•)ノ
We still have a second system, that can be used to test the latest ISO on UEFI 
mode

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

Well that worked for the block probing step :)

The device is now selectable and the installation process begins. :+1:

But the patched curtin (from your paste) seems to trip on a next error
during install:


Tags:  focal uec-images
Title: install failed crashed with CalledProcessError
Traceback:
 Traceback (most recent call last):
   File 
"/snap/subiquity/1999/lib/python3.6/site-packages/curtin/commands/main.py", 
line 202, in main
 ret = args.func(args)
   File 
"/snap/subiquity/1999/lib/python3.6/site-packages/curtin/commands/curthooks.py",
 line 1638, in curthooks
 builtin_curthooks(cfg, target, state)
   File 
"/snap/subiquity/1999/lib/python3.6/site-packages/curtin/commands/curthooks.py",
 line 1604, in builtin_curthooks
 setup_grub(cfg, target, osfamily=osfamily)
   File 
"/snap/subiquity/1999/lib/python3.6/site-packages/curtin/commands/curthooks.py",
 line 627, in setup_grub
 join_stdout_err + args + instdevs, env=env, capture=True)
   File "/snap/subiquity/1999/lib/python3.6/site-packages/curtin/util.py", line 
275, in subp
 return _subp(*args, **kwargs)
   File "/snap/subiquity/1999/lib/python3.6/site-packages/curtin/util.py", line 
141, in _subp
 cmd=args)
 curtin.util.ProcessExecutionError: Unexpected error while running command.


The install fail is attached.

Thank you for your commitment and patience, Michael!

** Attachment added: "1586336110.222144365.install_fail.crash"
   
https://bugs.launchpad.net/subiquity/+bug/1868109/+attachment/5349400/+files/1586336110.222144365.install_fail.crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

My colleague manually patched probert in the subiquity snap (fictional
snap revision 1999 based on 1626 and your PR above) and we get a
different stacktrace now.

** Attachment added: "probert patch applied"
   
https://bugs.launchpad.net/subiquity/+bug/1868109/+attachment/5348624/+files/subiquity-error.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

Even if my last comment was sent on April 1st - it was no joke :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: block probing fails with KeyError MAJOR

[Malte Kuhn]

Hi Michael,

would it help to grant you SSH access into the installation session
(daily-live current iso) on that machine?

Regards
Malte

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  block probing fails with KeyError MAJOR

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: Subiquity on Focal Live Server (current daily-live) crashes on block probe

[Malte Kuhn]

I'll attach just everything of /var/crash ;)
(Daily-live current ISO from yesterday and switch to subiquity snap edge 
channel)

** Attachment added: "var_crash.tar.xz"
   
https://bugs.launchpad.net/subiquity/+bug/1868109/+attachment/5342062/+files/var_crash.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  Subiquity on Focal Live Server (current daily-live) crashes on block
  probe

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: Subiquity on Focal Live Server (current daily-live) crashes on block probe

[Malte Kuhn]

The installation was tried with the Ubuntu Focal Live Server (daily-live 
current) from 26.03.2020
(SHA256SUM b5a94bedc6833f2fabc4cda091cdcb8f5b8b5633ece68740145cedf6ec89b137)

On a sidenote: Installing on a desktop system, cloning the disk (in this
case a Samsung 970 EVO NVMe M.2 SSD), transferring it onto the Samsung
PM1725b 3.2TB PCIe 3.0x8 (AIC), renders a usable system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  Subiquity on Focal Live Server (current daily-live) crashes on block
  probe

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: Subiquity on Focal Live Server (current daily-live) crashes on block probe

[Malte Kuhn]

Tried subiquity in the edge channel - no change in the installation process in 
this regard.
The block probe still fails. The report was send via subiquity reporting 
functionality 1585241307.605162859.block_probe_...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  Subiquity on Focal Live Server (current daily-live) crashes on block
  probe

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] Re: Subiquity on Focal Live Server (current daily-live) crashes on block probe

[Malte Kuhn]

@mwhudson : do you have any commands I should execute to confirm this?
Or is the Fix Committed Status not equal to "it will be on the next daily live 
disc"?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  Subiquity on Focal Live Server (current daily-live) crashes on block
  probe

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868109] [NEW] Subiquity on Focal Live Server (current daily-live) crashes on block probe

[Malte Kuhn]

Public bug reported:

We were unable to install Ubuntu Focal Live Server via subiquity in the 
daily-live iso from 17.03.2020 (SHA256SUM 
341d2990bab8d28a02414743eb45d74bb90771a8cc34ca0a792293cbbedfcecf).
Reason appears to be a failiure in the block device probing section.
ISO was loaded via IPMI as virtual device.

Expected Result:
Subiquity would list the NVMe(SSD) that is residing in the first PCIe Slot of 
the Mainboard.
Continuation of installation.

Current Result:
Crash of installation process, no listing of block devices.
See attached screencast.

Additional Information:
 Hardware Specs:
   Mainboard: Supermicro X11DPi-NT
   CPUs: 2 * Intel Xeon Gold 6226
   SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC)

 Installation log was sent via reporting functionality of subiquity.

** Affects: subiquity
 Importance: Undecided
 Status: New

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: pm1725b samsung supermicro x11dpi-nt

** Attachment added: "Screencast_2020-03-19_14:22:19.mp4"
   
https://bugs.launchpad.net/bugs/1868109/+attachment/5338809/+files/Screencast_2020-03-19_14%3A22%3A19.mp4

** Description changed:

- We were unable to install Ubuntu Focal Live Server via subiquiti in the 
daily-live iso from 17.02.2020.
+ We were unable to install Ubuntu Focal Live Server via subiquity in the 
daily-live iso from 17.02.2020.
  Reason appears to be a failiure in the block device probing section.
  ISO was loaded via IPMI as virtual device.
  
  Expected Result:
  Subiquity would list the NVMe(SSD) that is residing in the first PCIe Slot of 
the Mainboard.
  Continuation of installation.
  
  Current Result:
  Crash of installation process, no listing of block devices.
  See attached screencast.
  
+ Additional Information:
+  Hardware Specs:
+    Mainboard: Supermicro X11DPi-NT
+    CPUs: 2 * Intel Xeon Gold 6226
+    SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC)
  
- Additional Information:
-  Hardware Specs:
-Mainboard: Supermicro X11DPi-NT
-CPUs: 2 * Intel Xeon Gold 6226
-SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC)
- 
-  Installation log was sent via reporting functionality of subiquity.
+  Installation log was sent via reporting functionality of subiquity.

** Description changed:

- We were unable to install Ubuntu Focal Live Server via subiquity in the 
daily-live iso from 17.02.2020.
+ We were unable to install Ubuntu Focal Live Server via subiquity in the 
daily-live iso from 17.03.2020.
  Reason appears to be a failiure in the block device probing section.
  ISO was loaded via IPMI as virtual device.
  
  Expected Result:
  Subiquity would list the NVMe(SSD) that is residing in the first PCIe Slot of 
the Mainboard.
  Continuation of installation.
  
  Current Result:
  Crash of installation process, no listing of block devices.
  See attached screencast.
  
  Additional Information:
   Hardware Specs:
     Mainboard: Supermicro X11DPi-NT
     CPUs: 2 * Intel Xeon Gold 6226
     SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC)
  
   Installation log was sent via reporting functionality of subiquity.

** Description changed:

- We were unable to install Ubuntu Focal Live Server via subiquity in the 
daily-live iso from 17.03.2020.
+ We were unable to install Ubuntu Focal Live Server via subiquity in the 
daily-live iso from 17.03.2020 (SHA256SUM 
341d2990bab8d28a02414743eb45d74bb90771a8cc34ca0a792293cbbedfcecf).
  Reason appears to be a failiure in the block device probing section.
  ISO was loaded via IPMI as virtual device.
  
  Expected Result:
  Subiquity would list the NVMe(SSD) that is residing in the first PCIe Slot of 
the Mainboard.
  Continuation of installation.
  
  Current Result:
  Crash of installation process, no listing of block devices.
  See attached screencast.
  
  Additional Information:
   Hardware Specs:
     Mainboard: Supermicro X11DPi-NT
     CPUs: 2 * Intel Xeon Gold 6226
     SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC)
  
   Installation log was sent via reporting functionality of subiquity.

** Also affects: ubuntu
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109

Title:
  Subiquity on Focal Live Server (current daily-live) crashes on block
  probe

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840956] Re: qemu-user-static fails to install in WSL and LXD

[Malte Forkel]

While the fix allows one to configure qemu-user-static, it prevents the
installation of the binary formats. In WSL Debian Buster on Windows 10
Pro Build 18363.535, I managed to install the formats by changing the
value of --fix-binary from yes to no. I think this eventually should be
fixed in WSL, see https://github.com/Microsoft/WSL/issues/2103.

** Bug watch added: github.com/Microsoft/WSL/issues #2103
   https://github.com/Microsoft/WSL/issues/2103

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840956

Title:
  qemu-user-static fails to install in WSL and LXD

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846714] Re: Merge "BUG/MEDIUM: server: Also copy "check-sni" for server templates."

[Malte Schmidt]

Set up HAProxy with the attached configuration. The server-template
directive will generate 3 upstreams based on the DNS-answers for
letsencrypt.status.io. This is basic HAProxy DNS-service-discovery.

If you now check back with the stats socket or the webinterface, you
will notice that while the first upstream will be L7OK, all the
following upstreams are going to be L6RSP, doe to the fact that the
check-sni setting does not get replicated for any of the generated
upstreams than the first.

The patch fixes this so the check-sni argument gets applied to all
generated upstreams. With a patched version of HAProxy all the 3
upstreams will be L7OK.

** Attachment added: "HAProxy configuration with server-template"
   
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1846714/+attachment/5295763/+files/haproxy.cfg

** Changed in: haproxy (Ubuntu Bionic)
   Status: Triaged => New

** Changed in: haproxy (Ubuntu Disco)
   Status: Triaged => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846714

Title:
  Merge "BUG/MEDIUM: server: Also copy "check-sni" for server
  templates."

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846714] [NEW] Merge "BUG/MEDIUM: server: Also copy "check-sni" for server templates."

[Malte Schmidt]

Public bug reported:

The current HAProxy 1.8.8 supplied with Ubuntu Bionic and Disco contains
a bug when using the server-template functionality for generating
upstreams in combination with the check-sni setting.

The bug was fixed in upstream 1.8.17:
https://git.haproxy.org/?p=haproxy-1.8.git;a=commit;h=5b9c962725e8352189911f2bdac7e3fa14f73846

Could you please take the appropriate action?

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


** Tags: check-sni haproxy server-template

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846714

Title:
  Merge "BUG/MEDIUM: server: Also copy "check-sni" for server
  templates."

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME

[Malte Deiseroth]

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

I also have nvidia-430 and am affected by this bug. However judging from
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859 this
is sadly just one more bug on the pile of wont-fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822179

Title:
  Resuming from sleep breaks desktop and lock screen background in GNOME

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840221] [NEW] libcurl built without libssh2/sftp/scp support <= 18.04

[Malte Schmidt]

Public bug reported:

Recently I found that in distributions <=18.04 libcurl is built without
libssh2 and therefore does not support the sftp/scp protocols.

I am not sure if this is a bug, but maybe this should be added per
default as its the case on 19.10 for example.

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


** Tags: curl libcurl libssh2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840221

Title:
  libcurl built without libssh2/sftp/scp support <= 18.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

[Malte Hellmeier]

Exact same problem here with Ubuntu 18.04 and kernel Linux
4.18.0-16-generic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676912

Title:
  Kernel 4.9+ regression: Suspend - Freezing of tasks failed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

[Malte Schmidt]

I tested and can reproduce the problem with this combination:

Ubuntu 16.04, kernel 5.0.0-05.201903032031, driver 2.7.6-k, firmware
18.8.9

I set the tag accordingly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

[Malte Schmidt]

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780916] Re: Serious openssl bug crashes imaps sessions

[Malte Langermann]

a temporary solution is to set
tls_session_timeout: 0
in /etc/imapd.conf to disable tls session caching.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780916

Title:
  Serious openssl bug crashes imaps sessions

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780916] Re: Serious openssl bug crashes imaps sessions

[Malte Langermann]

still waiting for an update...
Is there an easy way to get a newer version for Ubuntu 18.04?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780916

Title:
  Serious openssl bug crashes imaps sessions

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

[Malte Schmidt]

Can anyone follow up on this?

I am ready to provide specific logs and try alternative
methods/workarounds on demand.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

[Malte Schmidt]

Unable to serve the logs via apport-collect due to policy restrictions.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1804953] Re: cyrus-imapd: crash with ssl login

[Malte Langermann]

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

** This bug has been marked a duplicate of bug 1780916
   Serious openssl bug crashes imaps sessions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804953

Title:
  cyrus-imapd: crash with ssl login

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811963] [NEW] Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

[Malte Schmidt]

Public bug reported:

After rebooting the physical server there is a 50/50 chance of all connected 
interfaces coming up. This affects Dell EMC R740's and R440's equipped with the 
X710 network cards.
As far as I noticed (~20 reboots on different machines), this happens only when 
using bonding (in this case active-backup or mode 1, did not test different 
modes yet). The networking-hardware on the other side shows the ports 
"connected". tcpdump shows frames being received, even if the interface is in 
"state DOWN".

Tried with:

Ubuntu 16.04, kernel 4.4.0-141, driver 2.7.26 (from the Intel-website), 
firmware 18.8.9
Ubuntu 16.04, kernel 4.4.0-141, driver 1.4.25-k, firmware 18.8.9
Ubuntu 16.04, kernel 4.15.0-43 (hwe), driver 2.1.14-k, firmware 18.8.9

The following excerpts are made using Intels driver in version 2.7.26,
therefore tainting the kernel, but the same happens using the original
kernel's version or the hardware enablement kernel's version.

Sporadic failure case:

[6.319226] i40e: loading out-of-tree module taints kernel.
[6.319227] i40e: loading out-of-tree module taints kernel.
[6.319422] i40e: module verification failed: signature and/or required key 
missing - tainting kernel
[6.410837] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver 
- version 2.7.26
[6.410838] i40e: Copyright(c) 2013 - 2018 Intel Corporation.
[6.423542] i40e :3b:00.0: fw 6.81.49447 api 1.7 nvm 6.80 0x80003d72 
18.8.9
[6.658526] i40e :3b:00.0: MAC address: ff:ff:ff:ff:ff:ff
[6.710391] i40e :3b:00.0: PCI-Express: Speed 8.0GT/s Width x8
[6.725692] i40e :3b:00.0: Features: PF-id[0] VFs: 64 VSIs: 2 QP: 40 RSS 
FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA
[6.750239] i40e :3b:00.1: fw 6.81.49447 api 1.7 nvm 6.80 0x80003d72 
18.8.9
[6.987874] i40e :3b:00.1: MAC address: ff:ff:ff:ff:ff:f1
[7.005397] i40e :3b:00.1 eth0: NIC Link is Up, 10 Gbps Full Duplex, 
Flow Control: None
[7.024993] i40e :3b:00.1: PCI-Express: Speed 8.0GT/s Width x8
[7.040298] i40e :3b:00.1: Features: PF-id[1] VFs: 64 VSIs: 2 QP: 40 RSS 
FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA
[7.054384] i40e :3b:00.1 enp59s0f1: renamed from eth0
[7.079613] i40e :3b:00.0 enp59s0f0: renamed from eth1
[9.788893] i40e :3b:00.0 enp59s0f0: already using mac address 
ff:ff:ff:ff:ff:ff
[9.819480] i40e :3b:00.1 enp59s0f1: set new mac address 
ff:ff:ff:ff:ff:ff

[9.728194] bond0: Setting MII monitoring interval to 100
[9.788690] bond0: Adding slave enp59s0f0
[9.805195] bond0: Enslaving enp59s0f0 as a backup interface with a down link
[9.819470] bond0: Adding slave enp59s0f1
[9.836360] bond0: making interface enp59s0f1 the new active one
[9.836614] bond0: Enslaving enp59s0f1 as an active interface with an up link

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: enp59s0f1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: enp59s0f0
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: ff:ff:ff:ff:ff:ff
Slave queue ID: 0

Slave Interface: enp59s0f1
MII Status: up
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: ff:ff:ff:ff:ff:f1
Slave queue ID: 0

4: enp59s0f0:  mtu 1500 qdisc mq 
master bond0 portid  state DOWN group default qlen 1000
link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
5: enp59s0f1:  mtu 1500 qdisc mq master 
bond0 portid fff1 state UP group default qlen 1000
link/ether ff:ff:ff:ff:ff:f1 brd ff:ff:ff:ff:ff:ff
6: bond0:  mtu 1500 qdisc noqueue state 
UP group default qlen 1000
link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet 123.123.123.123/24 brd 123.123.123.255 scope global bond0
   valid_lft forever preferred_lft forever
inet6 :::::/64 scope link 
   valid_lft forever preferred_lft forever

bond0 Link encap:Ethernet  HWaddr ff:ff:ff:ff:ff:ff  
  inet addr:123.123.123.123  Bcast:123.123.123.255  Mask:255.255.255.0
  inet6 addr: :::::/64 Scope:Link
  UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
  RX packets:4392 errors:0 dropped:10 overruns:0 frame:0
  TX packets:3585 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:443958 (443.9 KB)  TX bytes:1129305 (1.1 MB)

enp59s0f0 Link encap:Ethernet  HWaddr ff:ff:ff:ff:ff:ff  
  UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
  RX packets:10 errors:0 dropped:10 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:684 (684.0 B)  TX bytes:0 (0.0 B)

enp59s0f1 Link encap:Ethernet  HWaddr ff:ff:ff:ff:ff:ff  
  UP BROADCAST 

[Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

[Malte Schmidt]

** Attachment added: "version_signature"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811963/+attachment/5229569/+files/version.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

[Malte Schmidt]

** Attachment added: "lspci -v"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811963/+attachment/5229570/+files/lspci.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797895] Re: salt-minion won't start with openssl 1.1.1

[Malte Schmidt]

This also affects salt-ssh.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797895

Title:
  salt-minion won't start with openssl 1.1.1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Malte Schmidt]

Easy workaround which does not require another apt-setup.udeb:

d-i preseed/late_commandstring  \
in-target wget -q -O /etc/apt/trusted.gpg.d/bla.asc 
http://bla.de/bla.asc ; \
in-target sed -i '/keyword to uncomment specific line in file/s/^# *//' 
/etc/apt/sources.list ; \
in-target apt-get update ; \
in-target apt-get -y install packages to install ;

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754075

Title:
  apt-setup uses apt-key but probably should not anymore

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Malte Schmidt]

I guess every sysadmin installing an agent-based configuration
management system via di will experience this problem, too. Funny how
there was no progress on this in half a year.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754075

Title:
  apt-setup uses apt-key but probably should not anymore

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag

[Malte Schmidt]

The 4.4.0-136 from xenial-proposed seem to be working.

When will this make its way to xenial-updates?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789653

Title:
  regression with EXT4 file systems and meta_bg flag

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails

[Malte Swart via ubuntu-bugs]

I successfully use neutron-dynamic-routing-common, python-neutron-
dynamic-routing and neutron-bgp-dragent in version 2:12.0.0-0ubuntu1.1
(from bionic-proposed) on bionic to provide BGP peerings with Neutron
network routes.


Host with bgp-dragent:

> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic

> dpkg -l | grep Dynamic\ Routing
ii  neutron-bgp-dragent   2:12.0.0-0ubuntu1.1   all 
 OpenStack Neutron Dynamic Routing - Agent
ii  neutron-dynamic-routing-common2:12.0.0-0ubuntu1.1   all 
 OpenStack Neutron Dynamic Routing - common files
ii  python-neutron-dynamic-routing2:12.0.0-0ubuntu1.1   all 
 OpenStack Neutron Dynamic Routing - Python 2.7 library


Host with neutron-server:
> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic

> dpkg -l | grep Dynamic\ Routing
ii  python-neutron-dynamic-routing 2:12.0.0-0ubuntu1.1   all
  OpenStack Neutron Dynamic Routing - Python 2.7 library

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750121

Title:
  Dynamic routing: adding speaker to agent fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1750121/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770399] [NEW] package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1

[Malte]

Public bug reported:

This error occured directly after fresh install of ubuntu 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.9+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or 
directory: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 shim:amd64: Install
 shim-signed:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu May 10 14:41:09 2018
EFIBootMgr: BootOrder: 0005,0007,0008,0003,0006,0004
EFITables:
 Mai 10 14:43:47 htpc-2016 kernel: efi: EFI v2.50 by American Megatrends
 Mai 10 14:43:47 htpc-2016 kernel: efi:  ESRT=0x6dd86918  ACPI=0x6d9c5000  ACPI 
2.0=0x6d9c5000  SMBIOS=0xf05e0  SMBIOS 3.0=0xf0600  MPS=0xfc9d0 
 Mai 10 14:43:47 htpc-2016 kernel: secureboot: Secure boot could not be 
determined (mode 0)
 Mai 10 14:43:47 htpc-2016 kernel: esrt: Reserving ESRT space from 
0x6dd86918 to 0x6dd86950.
ErrorMessage: installed shim-signed package post-installation script subprocess 
returned error exit status 1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: shim-signed
Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: 
installed shim-signed package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shim-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770399

Title:
  package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade:
  installed shim-signed package post-installation script subprocess
  returned error exit status 1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1760377] Re: Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic

[Malte Schmidt]

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

Same problem with ubuntu 17.10 and Kernel 4.13.0-37 and 4.13.0-38. On
the latest 4.16.1 mainline-kernel the problem does not exist.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760377

Title:
  Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1380976] Re: Limiting queue disk space does not work, upgrade needed

[Malte Schmidt]

I confirmed this bug as it still affects 7.4.4-1ubuntu2.7 from trusty-
updates.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380976

Title:
  Limiting queue disk space does not work, upgrade needed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726064] [NEW] keyboard hanging after activating fcitx pinyin

[Malte Kleemeier]

Public bug reported:

Release: Ubuntu 17.10
Package: fcitx 1:4.2.9.1-6

When I tried to activate fcitx pinyin input method after a fresh install of 
17.10,
keyboard immediately stopped working. After rebooting and logging in again, the 
system became
completely unusable (mouse pointer on an empty black screen). This could be 
fixed by deleting
".xinputrc" in my home directory, but pinyin input still not working. Has 
anyone observed the
same problem?

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726064

Title:
  keyboard hanging after activating fcitx pinyin

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1673717] Re: rsyslog GnuTLS error -50

[Malte Schmidt]

Test case

Step 1:

Create a rsyslog-config using gtls:

/etc/rsyslog.d/10-tlstest.conf

Step 2:

To generate the needed ca-, key-, cert-files, follow the guide at
http://www.rsyslog.com/doc/v8-stable/tutorials/tls.html#certificates

Step 3:

Setup a client, which relays logs to the server that was just set up

Step 4:

Check the rsyslog-log for the errors mentioned in the initial post.


** Attachment added: "10-tlstest.conf"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+attachment/4973253/+files/10-tlstest.conf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673717

Title:
  rsyslog GnuTLS error -50

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1698880] [NEW] Horizontal line flickering

[Malte Koch]

Public bug reported:

When i'm scrolling or watching a video there is a horizontal line
flickering in the middle of the screen. It doesnt matter if i use an
external monitor or the monitor of my laptop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-77.98-lowlatency 4.4.59
Uname: Linux 4.4.0-77-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Mon Jun 19 18:08:04 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698880

Title:
  Horizontal line flickering

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Malte Finsterwalder]

Do you have an estiamte, when will the package will move from proposed
to a full release in Ubuntu 16.04?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687019

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1650877] Re: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary

[Malte Cornils]

Setting 
/etc/systemd/resolv.conf entry DNSSEC=no and enacting a sudo service 
systemd-resolved restart works around the problem for me. However, DNSSEC with 
the default (i.e. fallback) should still work.

Starting Firefox does not "fix" the problem for me, though.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650877

Title:
  systemd-resolved: resolve call failed: DNSSEC validation failed:
  failed-auxiliary

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1675192] Re: unbound forgets forwarder set via dhcp when config is reloaded

[Malte S. Stretz]

A good environment to test this is actually AWS where I noticed this :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675192

Title:
  unbound forgets forwarder set via dhcp when config is reloaded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1675192] Re: unbound forgets forwarder set via dhcp when config is reloaded

[Malte S. Stretz]

Thanks for triaging.  I think you are right, restarts loose the
forwarders as well.  At least most the time, I think I saw one instance
where it didn't happen but maybe the DHCP lease happened to be renewed
at the same time or I just imagined it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675192

Title:
  unbound forgets forwarder set via dhcp when config is reloaded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1675192] [NEW] unbound forgets forwarder set via dhcp when config is reloaded

[Malte S. Stretz]

Public bug reported:

unbound is integrated quite nicely with resolvconf.  When a system boots
up and eth0 is configured via dhcp and gets a DHCP server, the forwarder
is set properly.  When you restart unbound, the forwarder is set
properly as well.

But if you reload the config, the forwarder is forgotten since the
resolvconf update script isn't called:


root@ip-172-31-20-36:~# unbound-control forward
172.31.0.2
root@ip-172-31-20-36:~# service unbound reload
root@ip-172-31-20-36:~# unbound-control forward
off (using root hints)


root@ip-172-31-20-36:~# unbound-control forward 172.31.0.2
ok
root@ip-172-31-20-36:~# unbound-control forward
172.31.0.2
root@ip-172-31-20-36:~# service unbound restart
root@ip-172-31-20-36:~# unbound-control forward
172.31.0.2

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unbound 1.5.8-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Mar 22 21:38:25 2017
Ec2AMI: ami-5aee2235
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-central-1b
Ec2InstanceType: t2.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unbound
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ec2-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675192

Title:
  unbound forgets forwarder set via dhcp when config is reloaded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656702] [NEW] Download of fonts fails. Version 3.6 fixes the problem. Please upgrade the package

[Malte Finsterwalder]

Public bug reported:

When I try to install this version of the package I get an error, that the 
fonts can't be downloaded. This is a know problem and is fixed in the release 
3.6 of the package, which has already been released.
Please upgrade the LaunchPad version.

Thanks,
   Malte

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656702

Title:
  Download of fonts fails. Version 3.6 fixes the problem. Please upgrade
  the package

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1179257] Re: "Exception: No date tag found" in ubuntu-support-status

[Malte S. Stretz]

I reinstalled that system by now and haven't seen the issue again yet.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179257

Title:
   "Exception: No date tag found" in ubuntu-support-status

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580356] Re: OpenVPN causes reboot failure on Xenial in AWS

[Malte Zacharias]

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

I can confirm the above reports as well as the description in #1595822.
OpenVPN is started too early in the boot process. Cloud-Init will default to 
configure tun0 instead of the guests main network interface via dhcp. This 
breaks the cloud-init process.

** This bug has been marked a duplicate of bug 1598522
   openvpn starts before network is up in 16.04 this breaks networking in clouds

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580356

Title:
  OpenVPN causes reboot failure on Xenial in AWS

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1258422]

[Malte-e1]

Same here, currently I keep my laptop in front of my external monitor
and have set it up to be above the laptop monitor. Windows go under the
bottom panel. I have tried just disabling the laptop monitor, although I
sometimes need it or arranging screens horizontally although physically
they are arranged vertically. Very annoying. If wayland worked with dual
monitor, I'd just be using that but it still seems quite far from being
usable.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258422

Title:
  Maximized windows go under panel if panel attached to screen edge
  between two monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1258422/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1437454] Re: The first one is only working..nothing else

[Malte Jörgens]

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

I have had the same issue. It seems that the fix in #737915 is not that
permanent, as someone already pointed out there. The workaround to
export LC_NUMERIC=C did work for me though (German locale).

** This bug has been marked a duplicate of bug 737915
   projectM starts with a black screen instead of the visualization

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437454

Title:
  The first one is only working..nothing else

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1579730] Re: sshuttle dies with a SyntaxError

[Malte S. Stretz]

The sshuttle version from yakkety (0.78.0-1) works.  The server I try to
connect to is rather old so this is probably "Make server parts work
with old versions of Python. Fixes #81."

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

** Summary changed:

- sshuttle dies with a SyntaxError
+ sshuttle dies with a SyntaxError when connecting to older servers

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579730

Title:
  sshuttle dies with a SyntaxError when connecting to older servers

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1579730] Re: sshuttle dies with a SyntaxError

[Malte S. Stretz]

The current version of sshuttle is 0.78, maybe it is fixed there:
  https://pypi.python.org/pypi/sshuttle

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579730

Title:
  sshuttle dies with a SyntaxError

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1579730] Re: sshuttle dies with a SyntaxError

[Malte S. Stretz]

sshuttle changelog:
http://sshuttle.readthedocs.io/en/stable/changes.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579730

Title:
  sshuttle dies with a SyntaxError

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1579730] [NEW] sshuttle dies with a SyntaxError

[Malte S. Stretz]

Public bug reported:

I upgraded from wily to xenial a few days ago and now sshuttle is
broken:

sshuttle -r example.net 10.49.0.0/16
[local sudo] Password: 
Traceback (most recent call last):
  File "", line 1, in 
  File "assembler.py", line 22, in 
  File "sshuttle.helpers", line 73
except socket.error as e:
 ^
SyntaxError: invalid syntax
client: fatal: server died with error code 1

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: sshuttle 0.76-1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Mon May  9 13:42:13 2016
InstallationDate: Installed on 2016-01-03 (126 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: sshuttle
UpgradeStatus: Upgraded to xenial on 2016-05-07 (1 days ago)

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


** Tags: amd64 apport-bug xenial

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1579730/+attachment/4659176/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579730

Title:
  sshuttle dies with a SyntaxError

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1255794] Re: package steam (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Malte Pannemann]

happen to me try to install steam via Ubuntu Software 
"script returned error exit status 30"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255794

Title:
  package steam (not installed) failed to install/upgrade: subprocess
  new pre-installation script returned error exit status 128

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1255794] Re: package steam (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Malte Pannemann]

with Ubuntu 16.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255794

Title:
  package steam (not installed) failed to install/upgrade: subprocess
  new pre-installation script returned error exit status 128

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1494350] Re: QEMU: causes vCPU steal time overflow on live migration

[Malte S. Stretz]

** Also affects: linux (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785557
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494350

Title:
  QEMU: causes vCPU steal time overflow on live migration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374892] Re: Please backport php5-apcu version 4.0.6 to Ubuntu 14.04 LTS

[Malte]

I'm running MediaWiki (from Ubuntu packages) on a Ubuntu 14.04 LTS
installation with APCu enabled. I upgraded APCu to the
4.0.7-1build1~ubuntu14.04.1 version in trusty-backports. However, I'm
still getting hangs with stacktraces similar to this one:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_rwlock_wrlock () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_wrlock.S:85
85  ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_wrlock.S: No such 
file or directory.
#0  pthread_rwlock_wrlock () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_wrlock.S:85
#1  0x7f1d95f0ac84 in apc_lock_wlock () from /usr/lib/php5/20121212/apcu.so
#2  0x7f1d95f0eed8 in apc_cache_insert () from 
/usr/lib/php5/20121212/apcu.so
#3  0x7f1d95f0fb67 in apc_cache_store () from /usr/lib/php5/20121212/apcu.so
#4  0x7f1d95f0c61b in ?? () from /usr/lib/php5/20121212/apcu.so
#5  0x006ddbdb in dtrace_execute_internal ()

Reading https://github.com/krakjoe/apcu/issues/19 it looks like there
have been additional fixes in APCu 4.0.10 that are missing in 4.0.7 but
not sure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374892

Title:
  Please backport php5-apcu version 4.0.6 to Ubuntu 14.04 LTS

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1180649] Re: sbsigntool warning: file-aligned section .text extends beyond end of file; checksum areas are greater than image size. Invalid section table?

[Malte S. Stretz]

** Also affects: sbtools
   Importance: Undecided
   Status: New

** Summary changed:

- sbsigntool warning: file-aligned section .text extends beyond end of file; 
checksum areas are greater than image size. Invalid section table?
+ sbsigntool prints scary warning about invalid PE-COFF files which should be 
debug infos (file-aligned section .text extends beyond end of file; checksum 
areas are greater than image size. Invalid section table?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180649

Title:
  sbsigntool prints scary warning about invalid PE-COFF files which
  should be debug infos (file-aligned section .text extends beyond end
  of file; checksum areas are greater than image size. Invalid section
  table?)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1180649] Re: Setting up linux-signed-image-3.8.0-21-generic (3.8.0-21.32) ... warning: file-aligned section .text extends beyond end of file

[Malte S. Stretz]

I asked around and this is an overly verbose sbsigntool which should probably 
not a warning but a debug message:
https://twitter.com/mjg59/status/689745355202691073

** Package changed: linux-signed (Ubuntu) => sbsigntool (Ubuntu)

** Summary changed:

- Setting up linux-signed-image-3.8.0-21-generic (3.8.0-21.32) ... warning: 
file-aligned section .text extends beyond end of file
+ sbsigntool warning: file-aligned section .text extends beyond end of file; 
checksum areas are greater than image size. Invalid section table?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180649

Title:
  sbsigntool warning: file-aligned section .text extends beyond end of
  file; checksum areas are greater than image size. Invalid section
  table?

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530583] Re: Too small boot partition (and too large EFI partition) created with option "Use entire disk and set up encrypted LVM"

[Malte S. Stretz]

Ok, I understand the issue about the EFI partition. There is some rather long 
winder FDO spec which might allow reusing of the EFI partition for /boot 
purposes:
http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/

A boot partition of 256 MB is clearly too small for an EFI and/or Secure
Boot system though. (Even with /etc/kernel/postinst.d/apt-auto-removal
which should already do some housekeeping there.) If the EFI partition
can't be reused, the /boot partition should IMO be at least 512 MB (IIRC
that's also what the FDO spec recommends).

** Summary changed:

- Too small boot partition (and too large EFI partition) created with option 
"Use entire disk and set up encrypted LVM"
+ Too small boot partition created with option "Use entire disk and set up 
encrypted LVM"

** Summary changed:

- Too small boot partition created with option "Use entire disk and set up 
encrypted LVM"
+ Too small boot partition created with option "Use entire disk and set up 
encrypted LVM" in combination with UEFI Secure Boot

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530583

Title:
  Too small boot partition created with option "Use entire disk and set
  up encrypted LVM" in combination with UEFI Secure Boot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1531798] Re: subversion crashes in kwallet_password_set (libsvn_auth_kwallet)

[Malte S. Stretz]

I tried the packages from xenial (1.9.2-3ubuntu2) and the issue seems to
be fixed there (looks like KWallet isn't used anymore at all).

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531798

Title:
  subversion crashes in kwallet_password_set (libsvn_auth_kwallet)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1531798] [NEW] subversion crashes in kwallet_password_set (libsvn_auth_kwallet)

[Malte S. Stretz]

Public bug reported:

I've seen this issue for years (at least since precise) already: On
checkout, subversion always crashes with a Segmentation Fault. I've got
to cleanup and update the repo afterwards.

Being annoyed I finally attached gdb and got the following backtrace:

8<

Starting program: /usr/bin/svn co --username u0016 
https://repos.example.com/svn/p351/trunk broker
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Authentication realm:  Corp Repositories
Password for 'u0016': ***


Program received signal SIGSEGV, Segmentation fault.
0x709daf99 in kwallet_password_set (done=done@entry=0x7fffced4, 
creds=creds@entry=0x77fae0f0, realmstring=realmstring@entry=0x77fb7430 
" Corp Repositories", username=0x77f13458 
"u0016", 
password=0x77f13638 "***", 
parameters=parameters@entry=0x77fbe0a8, non_interactive=0, 
pool=0x77fba028) at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_auth_kwallet/kwallet.cpp:317
317 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_auth_kwallet/kwallet.cpp:
 No such file or directory.
(gdb) bt
#0  0x709daf99 in kwallet_password_set (done=done@entry=0x7fffced4, 
creds=creds@entry=0x77fae0f0, realmstring=realmstring@entry=0x77fb7430 
" Corp Repositories", username=0x77f13458 
"u0016", 
password=0x77f13638 "***", 
parameters=parameters@entry=0x77fbe0a8, non_interactive=0, 
pool=0x77fba028) at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_auth_kwallet/kwallet.cpp:317
#1  0x7705b3e7 in svn_auth__simple_creds_cache_set 
(saved=0x7fffced4, credentials=0x77f13228, provider_baton=0x0, 
parameters=0x77fbe0a8, realmstring=0x77fb7430 
" Corp Repositories", 
password_set=password_set@entry=0x709dad30 
, passtype=, pool=0x77fba028)
at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_subr/simple_providers.c:458
#2  0x709da94a in kwallet_simple_save_creds (saved=, 
credentials=, provider_baton=, 
parameters=, realmstring=, pool=)
at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_auth_kwallet/kwallet.cpp:372
#3  0x770326c5 in svn_auth_save_credentials (state=0x77fb7400, 
pool=0x77fba028) at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_subr/auth.c:379
#4  0x75fa2331 in handle_response (scratch_pool=, 
serf_status=, handler=0x77f18498, response=, request=0x77f10038) at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_ra_serf/util.c:2116
#5  handle_response_cb (request=0x77f10038, response=0x77f0e0b8, 
baton=0x77f18498, scratch_pool=0x77fa7028) at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_ra_serf/util.c:2275
#6  0x749c745e in serf.process_connection () from 
/usr/lib/x86_64-linux-gnu/libserf-1.so.1
#7  0x749c5cee in serf_event_trigger () from 
/usr/lib/x86_64-linux-gnu/libserf-1.so.1
#8  0x749c5e0c in serf_context_run () from 
/usr/lib/x86_64-linux-gnu/libserf-1.so.1
#9  0x75fa0b73 in svn_ra_serf__context_run_wait 
(done=done@entry=0x77f184b4, sess=0x77f18110, 
scratch_pool=scratch_pool@entry=0x77f18028) at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_ra_serf/util.c:917
#10 0x75fa1d34 in svn_ra_serf__context_run_one (handler=0x77f18498, 
scratch_pool=scratch_pool@entry=0x77f18028) at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_ra_serf/util.c:982
#11 0x75f94c30 in svn_ra_serf__exchange_capabilities 
(serf_sess=serf_sess@entry=0x77f18110, 
corrected_url=corrected_url@entry=0x7fffd398, 
pool=pool@entry=0x77f18028)
at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_ra_serf/options.c:494
#12 0x75f9a647 in svn_ra_serf__open (session=, 
corrected_url=0x7fffd398, session_URL=, 
callbacks=0x77fe30c8, callback_baton=, config=, pool=0x77f18028)
at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_ra_serf/serf.c:541
#13 0x776c485d in svn_ra_open4 
(session_p=session_p@entry=0x7fffd610, corrected_url_p=0x7fffd4e0, 
repos_URL=repos_URL@entry=0x77fe2d58 
"https://repos.example.com/svn/p351/trunk;, uuid=0x77fe3120 
"60787c2e-1572-4845-8071-d2064bb41626", 
callbacks=0x77fe30c8, 
callback_baton=callback_baton@entry=0x77fe30a0, config=0x77feacd8, 
pool=0x77fe1028) at 
/build/subversion-xd0hYD/subversion-1.8.13/subversion/libsvn_ra/ra_loader.c:479
#14 0x77bbe3c1 in svn_client__open_ra_session_internal 

[Bug 1530985] [NEW] RFE: Add ufw app profile for KDEConnect

[Malte S. Stretz]

Public bug reported:

If the kdeconnect package put a proper config file into
/etc/ufw/applications.d it would be possible to allow access to the
service via some simple commands. I'll attach such a file.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: kdeconnect 0.8-0ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jan  4 21:56:39 2016
InstallationDate: Installed on 2016-01-03 (1 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: kdeconnect
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530985

Title:
  RFE: Add ufw app profile for KDEConnect

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530985] Re: RFE: Add ufw app definition for KDEConnect

[Malte S. Stretz]

** Attachment added: "kdeconnect app definition"
   
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1530985/+attachment/4543961/+files/kdeconnect

** Summary changed:

- RFE: Add ufw app definition for KDEConnect
+ RFE: Add ufw app profile for KDEConnect

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530985

Title:
  RFE: Add ufw app profile for KDEConnect

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530653] Re: Manual Disk Setup doesn't work with LUKS ("physical volume for encryption")

[Malte S. Stretz]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530653

Title:
  Manual Disk Setup doesn't work with LUKS ("physical volume for
  encryption")

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530583] Re: Too small boot partition (and too large EFI partition) created with option "Use entire disk and set up encrypted LVM"

[Malte S. Stretz]

Not an installation but a design issue.

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

** Description changed:

- I (re)installed Kubuntu 14.10 with the partitioning option "Guided - Use
+ I (re)installed Kubuntu 15.10 with the partitioning option "Guided - Use
  entire disk and set up encrypted LVM" on an empty disk. After the final
  reboot, the partiton table shown below was created.
  
  The EFI partition was created with 512 MB and the boot partition with
  256 MB. From previous experiences is a 256 MB boot partition too small
  and tends to fill up with old kernels (it is filled up to 50% with only
  two kernels already). OTOH is a EFI partition with 512 MB quite big for
  the data usage I see.
  
  IMO the sizes would make more sense the other way round: 256 MB EFI and
  512 MB boot.
- 
  
  root@slpn-nb-mss:~# sfdisk -d /dev/sda
  label: gpt
  label-id: D6AB39C1-6A31-41D2-ADC7-7D8EBEADB20B
  device: /dev/sda
  unit: sectors
  first-lba: 34
  last-lba: 937703054
  
  /dev/sda1 : start=2048, size= 1048576, 
type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, 
uuid=DBE2960E-6316-4F84-9A04-53D1A80AF4B7, name="EFI System Partition"
  /dev/sda2 : start= 1050624, size=  499712, 
type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, 
uuid=9ABC6B6A-C4FA-4372-BF61-5713FA67F858
  /dev/sda3 : start= 1550336, size=   936151040, 
type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, 
uuid=D65DFD07-4F34-4CAE-B7F2-03040C2AE900
  root@slpn-nb-mss:~# df -h | grep /dev/sda
  /dev/sda2   237M  109M  116M  49% /boot
  /dev/sda1   511M  3,4M  508M   1% /boot/efi
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  Date: Sat Jan  2 21:41:01 2016
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2016-01-02 (0 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530583

Title:
  Too small boot partition (and too large EFI partition) created with
  option "Use entire disk and set up encrypted LVM"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530653] [NEW] Manual Disk Setup doesn't work with LUKS ("physical volume for encryption")

[Malte S. Stretz]

Public bug reported:

When installing Kubuntu 15.10 you can select Manual Partitioning/Disk
Setup. In the following dialog (cf. attached screenshot) you can select
a partition type "physical volume for encryption". But after that
there's no additional disk space popping up for further partitioning
like it did before (admittedly I last installed Kubuntu on Karmic).

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubiquity-frontend-kde 2.21.37 [modified: 
usr/share/applications/kde4/ubiquity-kdeui.desktop]
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CasperVersion: 1.365
CurrentDesktop: KDE
Date: Sun Jan  3 14:06:03 2016
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/kubuntu.seed 
boot=casper maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-2.21.37 wily

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1530653/+attachment/4543427/+files/ubiquity-kde-luks-fail.png

** Description changed:

- When installing Kubuntu 14.10 you can select Manual Partitioning/Disk
+ When installing Kubuntu 15.10 you can select Manual Partitioning/Disk
  Setup. In the following dialog (cf. attached screenshot) you can select
  a partition type "physical volume for encryption". But after that
  there's no additional disk space popping up for further partitioning
  like it did before (admittedly I last installed Kubuntu on Karmic).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ubiquity-frontend-kde 2.21.37 [modified: 
usr/share/applications/kde4/ubiquity-kdeui.desktop]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.365
  CurrentDesktop: KDE
  Date: Sun Jan  3 14:06:03 2016
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530653

Title:
  Manual Disk Setup doesn't work with LUKS ("physical volume for
  encryption")

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530583] [NEW] Too small boot partition (and too large EFI partition) created with option "Use entire disk and set up encrypted LVM"

[Malte S. Stretz]

Public bug reported:

I (re)installed Kubuntu 14.10 with the partitioning option "Guided - Use
entire disk and set up encrypted LVM" on an empty disk. After the final
reboot, the partiton table shown below was created.

The EFI partition was created with 512 MB and the boot partition with
256 MB. From previous experiences is a 256 MB boot partition too small
and tends to fill up with old kernels (it is filled up to 50% with only
two kernels already). OTOH is a EFI partition with 512 MB quite big for
the data usage I see.

IMO the sizes would make more sense the other way round: 256 MB EFI and
512 MB boot.


root@slpn-nb-mss:~# sfdisk -d /dev/sda
label: gpt
label-id: D6AB39C1-6A31-41D2-ADC7-7D8EBEADB20B
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 937703054

/dev/sda1 : start=2048, size= 1048576, 
type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, 
uuid=DBE2960E-6316-4F84-9A04-53D1A80AF4B7, name="EFI System Partition"
/dev/sda2 : start= 1050624, size=  499712, 
type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, 
uuid=9ABC6B6A-C4FA-4372-BF61-5713FA67F858
/dev/sda3 : start= 1550336, size=   936151040, 
type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, 
uuid=D65DFD07-4F34-4CAE-B7F2-03040C2AE900
root@slpn-nb-mss:~# df -h | grep /dev/sda
/dev/sda2   237M  109M  116M  49% /boot
/dev/sda1   511M  3,4M  508M   1% /boot/efi

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
Date: Sat Jan  2 21:41:01 2016
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/kubuntu.seed 
boot=casper maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2016-01-02 (0 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.37 wily

** Summary changed:

- Too small boot partition and too large EFI partition created with option "Use 
entire disk and set up encrypted LVM"
+ Too small boot partition (and too large EFI partition) created with option 
"Use entire disk and set up encrypted LVM"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530583

Title:
  Too small boot partition (and too large EFI partition) created with
  option "Use entire disk and set up encrypted LVM"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530346] [NEW] freeze after Kernel upgraded to 4.2.0-22

[Malte]

Public bug reported:

Ubuntu installed Kernel 4.2.0-22 via auto update.
After reboot the login screen came and the display resolution was set to maybe 
800x600, no mouse or keyboard input was possible and after a few seconds the 
password input stopped blinking and it seems that everything was frozen.
Booting up via selecting old Kernel in Grub is still possible.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
 GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Thu Dec 31 14:34:26 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
 nvidia-352, 352.63, 4.2.0-16-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:3669]
InstallationDate: Installed on 2015-12-30 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Dec 31 14:28:40 2015
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: amd64 apport-bug ubuntu wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530346

Title:
  freeze after Kernel upgraded to 4.2.0-22

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445616] Re: crmsh in vivid is not compatible with pacemaker

[Malte Langermann]

It is also wrong in Xenial.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445616

Title:
  crmsh in vivid is not compatible with pacemaker

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445616] Re: crmsh in vivid is not compatible with pacemaker

[Malte Langermann]

It is also wrong in Xenial.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to crmsh in Ubuntu.
https://bugs.launchpad.net/bugs/1445616

Title:
  crmsh in vivid is not compatible with pacemaker

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs