Re: [Touch-packages] [Bug 1981672] Re: phased updates API and client for aptitude

[Axel Beckert]

Hi Julian,

Julian Andres Klode wrote:
> Do note that aptitude is mostly unmaintained these days.

I have to object here as well:

There's no development currently, but it is _not_ unmaintained. (And
the current RC bug in Debian will soon be addressed. I'm just back
from holidays.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  phased updates API and client for aptitude

Status in apt package in Ubuntu:
  Triaged
Status in aptitude package in Ubuntu:
  Triaged

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

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


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

Re: [Touch-packages] [Bug 1981672] Re: apt phased out broken code, missing documentation to opt out

[Axel Beckert]

Hi Julian,

Julian Andres Klode wrote:
> aptitude is not a reliable tool that respects your choices like that
> (its solver will happily suggest solutions violating your wishes; it

I have to object here. It very well respects the user's wishes and
also has a setting where the user can configure it should propose
solutions violating holds and forbids.

> also generally is too happy to remove packages),

Again, this solely depends on your settings.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  phased updates API and client for aptitude

Status in apt package in Ubuntu:
  Triaged
Status in aptitude package in Ubuntu:
  Triaged

Bug description:
  Having the configuration at
  https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345/24
  it fails to work.

  The phased updates get distributed on some hosts anyways for 22.04.

  Please properly document and test this, and provide a working
  configuration to opt out from phased updates.

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


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

[Touch-packages] [Bug 1960727] Re: When apt holds back updates, it fails to inform the user of the reason

[Axel Beckert]

** Package changed: aptitude (Ubuntu) => apt (Ubuntu)

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

Title:
  When apt holds back updates, it fails to inform the user of the reason

Status in apt package in Ubuntu:
  New

Bug description:
  In the case where apt refuses to install and holds back certain
  packages, only the following output is produced:

  root@system:/home/admin# apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
[ List of packages ]
  0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.

  
  Missing is any explanation about which package is responsible for apt 
refusing to perform its job, or even what is the reason for that package being 
uninstallable.

  This bug leads users to believe that official Ubuntu packages are
  routinely misconstructed, corrupt, or otherwise junk.

  Fix: Instead of apt simply responding "No Dave, I'm Afraid I Can't Do
  that", correct the output to include the specific package that has a
  missing or unresolved dependency, so the user a) has confidence that
  the process works correctly and b) can proceed with fixing the
  problem.

  
  This bug is longstanding, so I don't think version details are required, but 
they follow anyway:

  1) Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  2) # apt --version
  apt 2.0.6 (amd64)

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


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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Axel Beckert]

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

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

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Fix Released
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Fix Released
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Incomplete
Status in zsh package in Debian:
  Unknown

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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


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

[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

Yes, that's exactly what I am doing. There is a work-around.

To have it in Wayland is a matter of comfort since I try to stay on
Wayland. It will be the future, right?

Thanks again.

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

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

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

[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

Thank you very much.

In which time-frame can I expect the fix being on my machine?
And how do I notice, can I check that it is here?

Sorry again for these questions, but I need to learn a lot how this
system works.

Best regards

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

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

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

[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

I'm using Ubuntu 19.10 Eoan Ermine.

Sorry I did not mention that.

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

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

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

[Touch-packages] [Bug 1851128] [NEW] Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

Public bug reported:

There is an issue in gtk. In Wayland sessions the use of a stylus leads
to crash of the application. It is apparently fixed in Gnome gtk.

When asking what should I do I got the answer that I should ask the
ubuntu gtk maintainers to  backport <
https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
, which I do
here and now.

Best regards

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

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Axel Beckert]

zsh is not really fixed. Please see the changelog entry of 5.6.2-3 which
states:

  * [92175749] Revert "Switch from the deprecated libpcre3 to the newer
(!) libpcre2." libpcre2 is not a drop-in replacement and not detected
by zsh's configure script. (Closes: #909084, reopens LP#1792544)

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Fix Released

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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

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

[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Axel Meunier]

I am also experiencing this bug. It should be noted that it does not
happen in Fedora 29 (it is mentioned here by a F29 user :
https://gitlab.gnome.org/GNOME/gtk/issues/1572 and I have also checked
it myself) so it seems to be Ubuntu specific.

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Axel Beckert]

Hi,

Andreas Hasenack wrote:
> I've seen the wget debian change, but just switching builddeps from pcre3-dev 
> to pcre2-dev and rebuilding isn't enough. The package ends up not finding 
> pcre and doesn't enable it:
> checking for PCRE... no
> checking pcre.h usability... no
> checking pcre.h presence... no
> checking for pcre.h... no
> ...
>   Libs:  -luuid -lidn2 -lnettle -lgnutls -lz -lpsl 
> 
> So while the package builds, it's not using pcre.
> 
> I tried to switch apache, and while I could make it find pcre2-config and use 
> it, pcre2 has different libraries than pcre3:
> pcre3-config --libs: -lpcre
> pcre2-config --libs: no such parameter
> 
> In pcre2, we have --libs8, --libs-posix, --libs32 and --libs16, but no
> --libs. Is this a bug in pcre2-config?

Indeed, same for zsh:

checking for pcre-config... no
checking pcre.h usability... no
checking pcre.h presence... no
checking for pcre.h... no
checking for pcre_compile... no
checking for pcre_study... no
checking for pcre_exec... no
[...]
../../Test/V07pcre.ztst: starting.
../../Test/V07pcre.ztst: skipped (the zsh/pcre module is not available)

→ Back to Incomplete. I'll revert that commit from the recent 5.6.2-2
  upload.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


** Changed in: zsh (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Axel Beckert]

zsh in Debian Unstable (5.6.2-1) seems to build fine if I exchange
libpcre3-dev by libpcre2-dev in Build-Depends and Build-Using (via
debian/rules).

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

Re: [Touch-packages] [Bug 1791811] Re: emacs ispell can't find german (deutsch) dictionary

[Axel G. Rossberg]

Thank you Roland.  So this was just an issue with Ubuntu not updating
the package...


From: Roland Rosenfeld 
Subject: [Bug 1791811] Re: emacs ispell can't find german (deutsch) dictionary
Date: Tue, 11 Sep 2018 15:24:04 -
Message-ID: <153667944478.24667.747378791142805.mal...@gac.canonical.com>

> 2018/09/11 16:30:52 (+0100) loganberry.canonical.com [127.0.0.1] => 
> loganberry.canonical.com
> 2018/09/11 16:30:52 (+0100) loganberry.canonical.com [91.189.90.37] => 
> indium.canonical.com
> 2018/09/11 16:30:54 (+0100) [91.189.90.7] => mx17.ispgateway.de
> 2018/09/11 16:30:55 (+0100) [80.67.18.18] => mailcluster2-8.ispgateway.de
> 2018/09/11 16:30:55 (+0100) sslmailpool.ispgateway.de [134.119.228.54] => 
> walnut
> 2018/09/11 16:30:55 (+0100) walnut [127.0.0.1] => pine

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

Title:
  emacs ispell can't find german (deutsch) dictionary

Status in igerman98 package in Ubuntu:
  New

Bug description:
  The ispell function of emacs expects to find a file such as
  /usr/lib/aspell/deutsch.alias, just as there is a file british.alias
  in the English aspell version. The file should probably simply contain
  the lines:

  # File added to make emacs ispell work
  add de_DE.multi

  Of course, as a simple workaround, you can add this file by hand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: aspell-de 20151222-1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 10 21:00:17 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-08-31 (9 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: igerman98
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791811] [NEW] emacs ispell can't find german (deutsch) dictionary

[Axel G. Rossberg]

Public bug reported:

The ispell function of emacs expects to find a file such as
/usr/lib/aspell/deutsch.alias, just as there is a file british.alias in
the English aspell version. The file should probably simply contain the
lines:

# File added to make emacs ispell work
add de_DE.multi

Of course, as a simple workaround, you can add this file by hand.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: aspell-de 20151222-1
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 10 21:00:17 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2018-08-31 (9 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
PackageArchitecture: all
SourcePackage: igerman98
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  emacs ispell can't find german (deutsch) dictionary

Status in igerman98 package in Ubuntu:
  New

Bug description:
  The ispell function of emacs expects to find a file such as
  /usr/lib/aspell/deutsch.alias, just as there is a file british.alias
  in the English aspell version. The file should probably simply contain
  the lines:

  # File added to make emacs ispell work
  add de_DE.multi

  Of course, as a simple workaround, you can add this file by hand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: aspell-de 20151222-1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 10 21:00:17 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-08-31 (9 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: igerman98
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

[axel]

On the same machine but on another disk with Manjaro I don't have these
errors. I think the problem can be solved by upgrading to the new
version of network-manager.

I installed new realtec driver but still no result.

Can you please upgrade network manager in Kubuntu 16.04? It slows down
my system start.

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

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

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

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

[axel]

I created this file with the above mentioned content but it doesn't work
for me. I still get error messages:

ntpdate[954]: name server cannot be used: Temporary failure in name resolution 
(-3)
cze 29 16:34:21 NetworkManager[879]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed

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

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

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

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

[axel]

There is a fix for this:
https://ubuntuforums.org/showthread.php?t=2305819

add a file to the /etc/modules-load.d directory to have the modules
loaded into the kernel at boot.  I just created a file called
netfilter.conf and put the following in it:

nf_nat_pptp
nf_conntrack_pptp
nf_conntrack_proto_gre


Is it safe to use this solution? I don't know what those three entries mean.

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

Title:
  nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

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

Bug description:
  Hello,
  On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3
  My WiFi connection is very unstable and I have to  often restart 
NetworkManager service (~ a dozen times every day...):

  sudo systemctl -l status NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago
   Main PID: 27832 (NetworkManager)
 Memory: 13.8M
CPU: 1.729s
 CGroup: /system.slice/NetworkManager.service
 ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-interfaces 
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid 
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
 ├─27832 /usr/sbin/NetworkManager --no-daemon
 └─30448 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf 
/run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf 
/var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease
 -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   keyfile: add 
connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0")
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 
20 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
device state change: unavailable -> disconnected (reason 'connection-assumed') 
[20 30 41]
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (lxcbr0): 
Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
new Tun device (carrier: OFF, driver: 'tun', ifindex: 34)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1): 
bridge port virbr1-nic was attached
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr1-nic): 
enslaved to virbr1
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   (virbr0): new 
Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29)
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: 
nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
  avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]:   failed to 
enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.ofono was not provided by any .service files

  Also, each time I restart my desktop, NetworkManager generates a crash 
report: cf. attached screenshots.
  I have tried an Ubuntu VM with the same packages related to networking and 
the exact same releases (same repositories), the crash never happens; the 
difference appears to be only the type of network connection: WiFi for the 
desktop vs Ethernet for the VM.

  Any suggestion?

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

[Axel]

Hmm... I've installed systemd 237-3ubuntu8.

Nevertheless I don't get forwarded to the captive-portal website to
login :-(.

What do I do wrong?

Axel

** Attachment added: "Forwarding to Captive-Portal login not working."
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+attachment/5117769/+files/Bildschirmfoto%20von%202018-04-16%2009-57-16.png

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  
  [Impact] 

   * Certain WiFi captive portals do not support EDNS0 queries, as per RFC.
   * Instead of responding with the captive portal IP address, they resond with 
domain not found
   * This prevents the user from hitting the captive portal login page, able to 
authenticate, and gain access to the internets.

  [The Fix]

   * As per tcp dumps, the problem arrises from receiving NXDOMAIN when queried 
with EDNS0
   * And receiving the right response without EDNS0
   * The solution was to downgrade transactions, and retry EDNS0 + NXDOMAIN 
result without EDNS0 with a hope of getting the right answer.

  [Test Case]

  * systemd-resolve securelogin.example.com
  * journalctl -b -u systemd-resolve | grep DVE-2018

  You should obverse that a warning message that transaction was retried
  with a reduced feature level e.g. UDP or TCP.

  After this test case is performed the result will be cached, therefore
  to revert to pristine state perform

  * systemd-resolve --flush-caches

  [Regression Potential]

   * The code retries, and then caches, NXDOMAIN results for certain
  queries (those that have 'secure' in them) with and without EDNS0.

   * Thus initial query for these domains may take longer, but hopefully
  will manage to receive the correct response.

   * Manufacturers are encouraged to correctly support EDNS0 queries,
  with flag D0 set to zero.

  [Other Info]
   
   * This issue is tracked as a dns-violation at
  
https://github.com/dns-violations/dns-violations/blob/master/2018/DVE-2018-0001.md

  [Original Bug report]

  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$

  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

[Axel]

@Mathieu,
Were the logs I sent you of any value to you for the debugging?

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Triaged

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

[Axel]

@ #19: Mathieu, 
I included the '234-2ubuntu12.3~mtrudel1' from the ppa you mention to my 
computer.
Unfortunately no change in behavior. I am still not forwarded to the captive 
portal after connecting to this particular wifi.
Do you have a suggestion what I could try?

@ #20: Does this: 'but it doesn't look like it helps.' mean that the new
systemd does not fix the bug and therefore it does not work on my side?

Axel

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Triaged

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

[Axel]

I would like to test it here with our public company-network that uses
securelogin.arubanetworks.com.

However, I run 17.10 on my laptop and installing the whole new systemd
235 from Bionic is not so straightforward I experienced. I gave up with
too many unfulfilled dependencies.

So could you give me instructions how to load this patch into Artful?

Thank you in advance.

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

[Axel]

Can we know what's the fix?

I apologize but I cannot recognize the patch in this thread.

I am running ubuntu 17.10 and am affected by a 
securelogin.arubanetworks.com-company-public-network.
I would like to test the fix.
How can I do that?

Thank you very much in advance.

Best regards

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1718841] [NEW] package libapparmor1:amd64 2.10.95-0ubuntu2.7 failed to install/upgrade: package libapparmor1:amd64 is not ready for configuration cannot configure (current status

[Axel Andres Valderrama Valderrama]

Public bug reported:

Error in the start

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libapparmor1:amd64 2.10.95-0ubuntu2.7
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Sep 21 18:30:24 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
DpkgTerminalLog:
 dpkg: error processing package libapparmor1:amd64 (--configure):
  package libapparmor1:amd64 is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package libapparmor1:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-09-21 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed 
root=UUID=922051bf-9077-47e0-8b11-082cc4e1c1ec ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: apparmor
Syslog:
 Sep 21 17:39:32 iter-PeCe dbus[789]: [system] AppArmor D-Bus mediation is 
enabled
 Sep 21 18:26:09 iter-PeCe dbus[802]: [system] AppArmor D-Bus mediation is 
enabled
 Sep 21 19:25:09 iter-PeCe dbus[782]: [system] AppArmor D-Bus mediation is 
enabled
Title: package libapparmor1:amd64 2.10.95-0ubuntu2.7 failed to install/upgrade: 
package libapparmor1:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libapparmor1:amd64 2.10.95-0ubuntu2.7 failed to
  install/upgrade: package libapparmor1:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in apparmor package in Ubuntu:
  New

Bug description:
  Error in the start

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libapparmor1:amd64 2.10.95-0ubuntu2.7
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep 21 18:30:24 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DpkgTerminalLog:
   dpkg: error processing package libapparmor1:amd64 (--configure):
package libapparmor1:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libapparmor1:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed 
root=UUID=922051bf-9077-47e0-8b11-082cc4e1c1ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apparmor
  Syslog:
   Sep 21 17:39:32 iter-PeCe dbus[789]: [system] AppArmor D-Bus mediation is 
enabled
   Sep 21 18:26:09 iter-PeCe dbus[802]: [system] AppArmor D-Bus mediation is 
enabled
   Sep 21 19:25:09 iter-PeCe dbus[782]: [system] AppArmor D-Bus mediation is 
enabled
  Title: package libapparmor1:amd64 2.10.95-0ubuntu2.7 failed to 
install/upgrade: package libapparmor1:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Axel Siebenwirth]

So, this has been going on for quite a while and still hasn't been
fixed?

I've got an DELL E5450 with an Intel Corporation Wireless 7265 wifi
adapter.

After resume from sleep wifi network does not reconnect nor does my
wireless network show up in the NM gui. But one other strangely enough
does and it's always a different one.

See attached log and screenshot.

Is there any proposed official workaround at least?


** Attachment added: "Syslog from before and after sleep"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4805755/+files/syslog_before_and_after_sleep.txt

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

[Touch-packages] [Bug 1055551] Re: zsh can causes ps to generate error message

[Axel Beckert]

Yes, this does no more appear in at least 16.04 Xenial. And Xenial has
procps 3.3.10 which should have fixed this issue. Hence closing. Thanks
for the hint.

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

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

Title:
  zsh can causes ps to generate error message

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  (ps|grep foo;echo)
  Signal 18 (CONT) caught by ps (procps-ng version 3.3.3).
  ps:display.c:59: please report this bug

  
  (ps;echo)  # works
  (ps|grep foo) # works
  (ps|grep foo;echo) # fails

  This behaviour seems to be caused by zsh since it is not observable
  using bash. Note too that this bug cannot be recreated on precise.

  zsh configuration is stock "system configuration" (run zsh for first
  time and select option (2) - system defaults).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: zsh 5.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  Date: Mon Sep 24 16:01:37 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120530)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: zsh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1580882] Re: [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

[John Axel Eriksson]

Early indications here are that updating the ALSA drivers fixes the
problem. I've usually noticed the problem when coming in to work and the
machine has been suspended, I did that whole thing now and reconnected
external display + headphones and I got proper sound. Seems promising.

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

Title:
  [Intel Broadwell HDMI, Digital Out] Sound like half speed after
  suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1580882] Re: [, Intel Broadwell HDMI, Digital Out, HDMI] Sound like half speed

[John Axel Eriksson]

Actually, I can add that it isn't only when connected via headphones. If
I connect to my TV at home and play a movie for example, the same thing
happens - sound is seemingly half speed. Just mentioning this since it
indicates it is entirely a problem with HDMI rather than headphones +
hdmi combo. A restart while connected via HDMI works around the issue in
this instance as well.

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

Title:
  [, Intel Broadwell HDMI, Digital Out, HDMI] Sound like half speed

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1580882] Re: [, Intel Broadwell HDMI, Digital Out, HDMI] Sound like half speed

[John Axel Eriksson]

Same problem here. Asus Laptop UX305fa. Half-speed sound when connected via 3.5 
mm to external monitor conntected via HDMI.
For me this started happening after upgrading from 15.10 to 16.04. I can get 
around the issue by rebooting my machine after connecting the external 
monitor... which ofc isn't a solution, just an ugly workaround for now.

cat /proc/asound/cards
 0 [HDMI   ]: HDA-Intel - HDA Intel HDMI
  HDA Intel HDMI at 0xf711c000 irq 50
 1 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xf7118000 irq 47

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

Title:
  [, Intel Broadwell HDMI, Digital Out, HDMI] Sound like half speed

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1579319] Re: Text missing in GTK+ applications after suspend

[Axel G. Rossberg]

Some people say this is not an xorg problem, but is a but in the kernel. 
https://bbs.archlinux.org/viewtopic.php?id=209065
Indeed, I have this problem when booting the 4.2.0 and 4.2.0 kernel, but not 
when booting 3.19.0.

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

Title:
  Text missing in GTK+ applications after suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Occasionally when resuming from suspend, text is randomly missing in
  GTK+ applications. Chrome and QT apps are unaffected. In my case it
  doesn't occur very frequently, perhaps once a week at most. I
  typically suspend my system every day and only reboot once or twice a
  month.

  It's not clear what is causing the problem. Based on the symptoms and
  similar bug reports, it seems most likely a problem with xorg and/or
  xserver-xorg-video-intel. It appears to be a new bug with 16.04 as I
  never experienced this in 15.10.

  I've noticed that the amount of missing text seems to vary depending
  on the font and font size. Some fonts/sizes seem to be okay, while
  with others there is no text on screen at all.

  Font rendering settings also appear have an effect. The problem is
  only visible with slight hinting and RGB sub pixel order. Disabling
  anti-aliasing or changing either the hinting or sub pixel order to
  anything else immediately renders all characters normally.

  Switching to a virtual terminal and back again fixes the problem
  (Ctrl+Alt+F1 then Ctrl+Alt+F7), as does restarting Xorg or logging
  out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat May  7 12:39:24 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:013c]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:013c]
  InstallationDate: Installed on 2016-04-23 (13 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Extensa 5230
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=ba619ff4-ea0b-4b58-aa61-e79a3e7e7c1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.28
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd02/02/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5230
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 02:12:16 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   15105 
   vendor LPL
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1495274] Re: python app crashes when using qt4-qtconfig

[axel]

Discussion 
https://anki.tenderapp.com/discussions/ankidesktop/18360-anki-keeps-crashing-on-kubuntu-1604

bug report on qt bugs
https://bugreports.qt.io/browse/QTBUG-53592

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

Title:
  python app crashes when using qt4-qtconfig

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  When I use qt4-qtconfig to set qtcurve as theme phython app Anki
  crashes or hangs. It happens for example when I click on File menu or
  Close button, etc.

  I described it also on Anki support forum
  https://anki.tenderapp.com/discussions/ankidesktop/14722-anki-crashes-on-linux

  On this forum they claim it is qtcurve problem but other applications
  that use qtcurve don't crash nor hang. So I suspect it is caused by
  qt4-qtconfig.

  report:
  http://pastebin.com/B85PP9sA

  I uninstalled qt4-qtconfig and there was no problem with Anki, no
  crashes or hangs, but without it I can't use this theme engine for all
  applications, for example without it Anki and also Kate uses Oxygen
  even when in KDE setting there is qtcurve style chosen.

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

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

[Touch-packages] [Bug 1495274] Re: python app crashes when using qt4-qtconfig

[axel]

** Attachment added: "new Anki crash reports from KDE4 and Plasma5 on Kubuntu 
16.04"
   
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1495274/+attachment/4669481/+files/Anki%20crash%20report

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

Title:
  python app crashes when using qt4-qtconfig

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  When I use qt4-qtconfig to set qtcurve as theme phython app Anki
  crashes or hangs. It happens for example when I click on File menu or
  Close button, etc.

  I described it also on Anki support forum
  https://anki.tenderapp.com/discussions/ankidesktop/14722-anki-crashes-on-linux

  On this forum they claim it is qtcurve problem but other applications
  that use qtcurve don't crash nor hang. So I suspect it is caused by
  qt4-qtconfig.

  report:
  http://pastebin.com/B85PP9sA

  I uninstalled qt4-qtconfig and there was no problem with Anki, no
  crashes or hangs, but without it I can't use this theme engine for all
  applications, for example without it Anki and also Kate uses Oxygen
  even when in KDE setting there is qtcurve style chosen.

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

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

[Touch-packages] [Bug 1559245] Re: Pulseaudio selects HSP instead of A2DP and no way to set default action

[Axel "Black Eco" Leroy]

I run with the same problem with my bluetooth speaker. Everytime I pair
it to my computer, GNOME Sound Setings defaults it to HSP/HSF and it
doesn't even register when I select A2DP, leaving me only with HSP/HSF
and its terrible sound quality.

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

Title:
  Pulseaudio selects HSP instead of A2DP and no way to set default
  action

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I am trying to use a bluetooth headphone with ubuntu 14.04 and system
  defaults to using HSP. The problem is that Once it connects, it should
  use A2DP and become default device because I am using it from KODI and
  it is very inconvenient to set it from command line. Otherwise HSP is
  providing very bad quality audio. There is no way to set a default
  action, and system does not retain the last set setting. Eg. I can go
  and set the headphones to use A2DP but when I connect next time, it
  switches back to HSP. (I believe it could remember the device from the
  device id at least!)

  I asked about this on launchpad answers and somebody closed it and said I 
should report it as a bug. If you think this shouldn't have been reported as a 
bug, blame the person who closed my question at launchpad answers :) Below is 
the link to it and more information and the ugly workaround I implemented in my 
system:
  https://answers.launchpad.net/ubuntu/+question/288799

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

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

[Touch-packages] [Bug 1562279] Re: Can't set en_NZ locale

[axel]

My problem is fixed. Solution here
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1560577
Restarting system might be needed.

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

Title:
  Can't set en_NZ locale

Status in language-pack-en-base package in Ubuntu:
  Confirmed

Bug description:
  After updating language-pack-en and language-pack-en-base in Xubuntu
  16.04, I can no longer set en_NZ.UTF-8 as my locale in lightdm-
  greeter.

  Current locale, after fiddling with language support, is:

  LANG=en_US.UTF-8
  LANGUAGE=en
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_NZ.UTF-8
  LC_TIME=en_NZ.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_NZ.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_NZ.UTF-8
  LC_NAME=en_NZ.UTF-8
  LC_ADDRESS=en_NZ.UTF-8
  LC_TELEPHONE=en_NZ.UTF-8
  LC_MEASUREMENT=en_NZ.UTF-8
  LC_IDENTIFICATION=en_NZ.UTF-8
  LC_ALL=

  Previously, everything was "en_NZ.UTF-8"

  I imagine that the same issue is going to apply to a number of
  English-language locales other than Australia, Canada, UK and US.
  These four, plus a generic "en" (which appears to default to en_US)
  are all that are displayed in the lightdm-greeter language menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1562279/+subscriptions

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

[Touch-packages] [Bug 1562279] Re: Can't set en_NZ locale

[axel]

I think I am also affected. I get in xenial 64-bit for xfce and ubuntu-
mate-core:

locale -a
C
C.UTF-8
POSIX
en_AG
en_AG.utf8
en_AU.utf8
en_BW.utf8
en_CA.utf8
en_GB.utf8
en_HK.utf8
en_IE.utf8
en_NZ.utf8
en_PH.utf8
en_SG.utf8
en_US.utf8
en_ZA.utf8
en_ZM
en_ZM.utf8
en_ZW.utf8


Although I installed 
language-pack-gnome-pl
language-pack-gnome-pl-base
language-pack-pl
language-pack-pl-base

I set pl_PL with 
sudo dpkg-reconfigure locales
and later also in Mate languages setting 
In Mausepad or Pluma and LibreOffice I do get Polish letters  but Mate 
interface is still in English. 

In Mate language support Polish is not even listed (not visible as
installed).

I also have problems with typing in Polish in wine. I don't know if this is 
related but might be. 
https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1563961

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

Title:
  Can't set en_NZ locale

Status in language-pack-en-base package in Ubuntu:
  Confirmed

Bug description:
  After updating language-pack-en and language-pack-en-base in Xubuntu
  16.04, I can no longer set en_NZ.UTF-8 as my locale in lightdm-
  greeter.

  Current locale, after fiddling with language support, is:

  LANG=en_US.UTF-8
  LANGUAGE=en
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_NZ.UTF-8
  LC_TIME=en_NZ.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_NZ.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_NZ.UTF-8
  LC_NAME=en_NZ.UTF-8
  LC_ADDRESS=en_NZ.UTF-8
  LC_TELEPHONE=en_NZ.UTF-8
  LC_MEASUREMENT=en_NZ.UTF-8
  LC_IDENTIFICATION=en_NZ.UTF-8
  LC_ALL=

  Previously, everything was "en_NZ.UTF-8"

  I imagine that the same issue is going to apply to a number of
  English-language locales other than Australia, Canada, UK and US.
  These four, plus a generic "en" (which appears to default to en_US)
  are all that are displayed in the lightdm-greeter language menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1562279/+subscriptions

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

[Touch-packages] [Bug 1562279] Re: Can't set en_NZ locale

[axel]

locale   
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=
LANGUAGE=
LC_CTYPE="POSIX"
LC_NUMERIC=pl_PL.UTF-8
LC_TIME=pl_PL.UTF-8
LC_COLLATE="POSIX"
LC_MONETARY=pl_PL.UTF-8
LC_MESSAGES="POSIX"
LC_PAPER=pl_PL.UTF-8
LC_NAME=pl_PL.UTF-8
LC_ADDRESS=pl_PL.UTF-8
LC_TELEPHONE=pl_PL.UTF-8
LC_MEASUREMENT=pl_PL.UTF-8
LC_IDENTIFICATION=pl_PL.UTF-8
LC_ALL=

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

Title:
  Can't set en_NZ locale

Status in language-pack-en-base package in Ubuntu:
  Confirmed

Bug description:
  After updating language-pack-en and language-pack-en-base in Xubuntu
  16.04, I can no longer set en_NZ.UTF-8 as my locale in lightdm-
  greeter.

  Current locale, after fiddling with language support, is:

  LANG=en_US.UTF-8
  LANGUAGE=en
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_NZ.UTF-8
  LC_TIME=en_NZ.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_NZ.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_NZ.UTF-8
  LC_NAME=en_NZ.UTF-8
  LC_ADDRESS=en_NZ.UTF-8
  LC_TELEPHONE=en_NZ.UTF-8
  LC_MEASUREMENT=en_NZ.UTF-8
  LC_IDENTIFICATION=en_NZ.UTF-8
  LC_ALL=

  Previously, everything was "en_NZ.UTF-8"

  I imagine that the same issue is going to apply to a number of
  English-language locales other than Australia, Canada, UK and US.
  These four, plus a generic "en" (which appears to default to en_US)
  are all that are displayed in the lightdm-greeter language menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1562279/+subscriptions

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

[Touch-packages] [Bug 1503382] Re: unable to install python3.4 dev on fresh ubuntu cloud image

[Axel Beckert]

This issue has been caused because the python3.4 upload to trusty-
updates from 24th of September has been reverted yesterday and has been
replaced by the previous upload. See
https://bugs.launchpad.net/bugs/1500768

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

Title:
  unable to install python3.4 dev on fresh ubuntu cloud image

Status in python3.4 package in Ubuntu:
  Confirmed

Bug description:
  Latest cloud ubuntu trusty image (06-Oct-2015 10:34)  https://cloud-
  images.ubuntu.com/trusty/current/

  apt-get update && apt-get upgrade # works fine

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

  The following packages have unmet dependencies:
   python3.4-dev : Depends: python3.4 (= 3.4.0-2ubuntu1.1) but 
3.4.3-1ubuntu1~14.04.1 is to be installed
   Depends: libpython3.4-dev (= 3.4.0-2ubuntu1.1) but it is not 
going to be installed
   Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

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

  The following packages have unmet dependencies:
   libpython3.4-dev : Depends: libpython3.4-stdlib (= 3.4.0-2ubuntu1.1) but 
3.4.3-1ubuntu1~14.04.1 is to be installed
  Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python3.4-dev (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Tue Oct  6 17:36:17 2015
  SourcePackage: python3.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests

[Axel Beckert]

So you leave all users of the trusty-updates with packages installed
that are newer than what is available in the archives and hence take the
chance to get proper security updates in the future?

# apt-cache policy python3.4
python3.4:
  Installed: 3.4.3-1ubuntu1~14.04.1
  Candidate: 3.4.3-1ubuntu1~14.04.1
  Version table:
 *** 3.4.3-1ubuntu1~14.04.1 0
100 /var/lib/dpkg/status
 3.4.0-2ubuntu1.1 0
500 http://ubuntu.ethz.ch/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 3.4.0-2ubuntu1 0
500 http://ubuntu.ethz.ch/ubuntu/ trusty/main amd64 Packages

Please do reverting in the future _only_ by uploading a package with
properly increased version number, e.g.
3.4.3+really3.4.0-0ubuntu1~14.04.1.

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

Title:
  python3.4.3 SRU break requests

Status in python3.4 package in Ubuntu:
  Triaged
Status in python3.4 source package in Trusty:
  Triaged

Bug description:
  Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using 
a squid proxy:
  
https://jenkins.qa.ubuntu.com/view/All/job/udtc-trusty-tests/1946/label=ps-trusty-desktop-amd64-1,type=large/testReport/tests.large.test_android/AndroidSDKTests/test_default_android_sdk_install/

  The code is using python-requests, with verify=True for ssl connection
  (default). Some tests are testing that invalid certificates are
  rejected:  https://github.com/ubuntu/ubuntu-
  make/blob/master/umake/network/download_center.py#L129

  Rerunning the same code with previous trusty package (3.4.0~trusty1)
  doesn't show up this issue. It seems that SNI is broken for the trusty
  version of python3-requests with 3.4.3. (See the FAQ http://www
  .python-requests.org/en/latest/community/faq/ with "What are “hostname
  doesn’t match” errors?" and the stackoverflow question.

  I did run a test, grabbing requests 2.7 and backporting it to trusty
  (I needed to as well to take python3-urllib3 willy version).

  So, 3.4.3 has an incompatible change for existing projects and people
  with proxys are starting to see some breakage like in
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1499890.

  Can we get it fix somehow, reverting the incompatible change breaking
  SNI (I wonder if this is "Changed in version 3.4.3: This class now
  performs all the necessary certificate and hostname checks by default.
  To revert to the previous, unverified, behavior
  ssl._create_unverified_context() can be passed to the context
  parameter." in https://docs.python.org/3/library/http.client.html or
  something else) so that existing code can either get a new compatible
  python-requests or avoid incompatible changes in python 3.4.3?

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

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

Re: [Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests

[Axel Beckert]

Hi Oli,

Oli wrote:
> I understand that this is a WiP and this has been done to stop more
> people hitting this issue, but is there a good way to downgrade to the
> last version temporarily?

We used "apt-get install -y --force-yes
python3.4{,-minimal}=3.4.0-2ubuntu1.1
libpython3.4{,-minimal,-stdlib}=3.4.0-2ubuntu1.1".

You might want to adjust the list of packages depending on which
packages you have installed. (Usage of "{…,…}" requires bash, zsh or
similar as shell.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  python3.4.3 SRU break requests

Status in python3.4 package in Ubuntu:
  Triaged
Status in python3.4 source package in Trusty:
  Triaged

Bug description:
  Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using 
a squid proxy:
  
https://jenkins.qa.ubuntu.com/view/All/job/udtc-trusty-tests/1946/label=ps-trusty-desktop-amd64-1,type=large/testReport/tests.large.test_android/AndroidSDKTests/test_default_android_sdk_install/

  The code is using python-requests, with verify=True for ssl connection
  (default). Some tests are testing that invalid certificates are
  rejected:  https://github.com/ubuntu/ubuntu-
  make/blob/master/umake/network/download_center.py#L129

  Rerunning the same code with previous trusty package (3.4.0~trusty1)
  doesn't show up this issue. It seems that SNI is broken for the trusty
  version of python3-requests with 3.4.3. (See the FAQ http://www
  .python-requests.org/en/latest/community/faq/ with "What are “hostname
  doesn’t match” errors?" and the stackoverflow question.

  I did run a test, grabbing requests 2.7 and backporting it to trusty
  (I needed to as well to take python3-urllib3 willy version).

  So, 3.4.3 has an incompatible change for existing projects and people
  with proxys are starting to see some breakage like in
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1499890.

  Can we get it fix somehow, reverting the incompatible change breaking
  SNI (I wonder if this is "Changed in version 3.4.3: This class now
  performs all the necessary certificate and hostname checks by default.
  To revert to the previous, unverified, behavior
  ssl._create_unverified_context() can be passed to the context
  parameter." in https://docs.python.org/3/library/http.client.html or
  something else) so that existing code can either get a new compatible
  python-requests or avoid incompatible changes in python 3.4.3?

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

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

[Touch-packages] [Bug 1432171] Re: [udev] Shows "starting version 219" boot message even with "quiet"

[axel]

I ran into this bug after a successfully logged in, could be a few hours or 
days latter without restarting, but suddenly session stop and I can see the 
black screen with "starting version 219" after that login screen appears again 
and I can start a new session but opened programs in the previous session still 
are running and I need to reboot to do a clean close of the applications left 
open in the former session.
I'm using Ubuntu Gnome 15.04 updated to the last software update message. Is 
there a way to solve this?. As additional info I could said that I boot from 
disk drive, without a proper UEFI boot because does not work(grub error) when I 
install it. At the beginning I need to select the drive boot but after a while 
I load without that step, maybe I select it as default but I don't remember.

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

Title:
  [udev] Shows "starting version 219" boot message even with "quiet"

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Everytime the system is booted up I get a "Starting version 219" which
  it seems is the version number for systemd.

  udev version: 219-4ubuntu5

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

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

[Touch-packages] [Bug 1495274] [NEW] python app crashes when using qt4-qtconfig

[axel]

Public bug reported:

When I use qt4-qtconfig to set qtcurve as theme phython app Anki crashes
or hangs. It happens for example when I click on File menu or Close
button, etc.

I described it also on Anki support forum
https://anki.tenderapp.com/discussions/ankidesktop/14722-anki-crashes-on-linux

On this forum they claim it is qtcurve problem but other applications
that use qtcurve don't crash nor hang. So I suspect it is caused by
qt4-qtconfig.

report:
http://pastebin.com/B85PP9sA

I uninstalled qt4-qtconfig and there was no problem with Anki, no
crashes or hangs, but without it I can't use this theme engine for all
applications, for example without it Anki and also Kate uses Oxygen even
when in KDE setting there is qtcurve style chosen.

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  python app crashes when using qt4-qtconfig

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  When I use qt4-qtconfig to set qtcurve as theme phython app Anki
  crashes or hangs. It happens for example when I click on File menu or
  Close button, etc.

  I described it also on Anki support forum
  https://anki.tenderapp.com/discussions/ankidesktop/14722-anki-crashes-on-linux

  On this forum they claim it is qtcurve problem but other applications
  that use qtcurve don't crash nor hang. So I suspect it is caused by
  qt4-qtconfig.

  report:
  http://pastebin.com/B85PP9sA

  I uninstalled qt4-qtconfig and there was no problem with Anki, no
  crashes or hangs, but without it I can't use this theme engine for all
  applications, for example without it Anki and also Kate uses Oxygen
  even when in KDE setting there is qtcurve style chosen.

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

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

[Touch-packages] [Bug 1495274] Re: python app crashes when using qt4-qtconfig

[axel]

I forgot to give details. It happens on Kubuntu 14.04 64-bit. Anki 2.0.32
Qt 4.8.6 PyQt 4.10.4

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

Title:
  python app crashes when using qt4-qtconfig

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  When I use qt4-qtconfig to set qtcurve as theme phython app Anki
  crashes or hangs. It happens for example when I click on File menu or
  Close button, etc.

  I described it also on Anki support forum
  https://anki.tenderapp.com/discussions/ankidesktop/14722-anki-crashes-on-linux

  On this forum they claim it is qtcurve problem but other applications
  that use qtcurve don't crash nor hang. So I suspect it is caused by
  qt4-qtconfig.

  report:
  http://pastebin.com/B85PP9sA

  I uninstalled qt4-qtconfig and there was no problem with Anki, no
  crashes or hangs, but without it I can't use this theme engine for all
  applications, for example without it Anki and also Kate uses Oxygen
  even when in KDE setting there is qtcurve style chosen.

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

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

[Touch-packages] [Bug 1008539] Re: Wrong volume binding when connecting bluetooth speakers

[Axel G. Rossberg]

Problem persists until today, first solution by Andrei works (add load-
module module-switch-on-connect in /etc/pulse/default.pa).

Let me just add that I had to reboot the system for the changes to take
effect.

I'd also suggest to ubuntu to add the line by default.

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

Title:
  Wrong volume binding when connecting bluetooth speakers

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a 2.1 speaker system and a Logitech bluetooth adapter for them that 
connects to my Asus UL50AG notebook for sound.
  In Sound Settings, I then have 2 entries: Built-in Audio Card and Logitech 
Adapter.

  The problem is that when I connect/reconnect to the bluetooth adapter,
  the sound volume knob is not bound to the Logitech Adapter. Instead,
  in Sound Settings, the Built-in Audio Card is selected instead of the
  Logitech Adapter. And when I use the multimedia keys on my notebook
  (Volume Up, Down, Mute), they have effect on the sound coming out of
  the notebook, not the external speakers.

  The expected result would be that, when I connect/reconnect the
  bluetooth adapter, the volume multimedia keys should bound to the new
  bluetooth setup, not the internal audio.

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

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

[Touch-packages] [Bug 1448259] Re: Systemd does not send SIGTERM first on shutdown

[Axel Beckert]

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

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

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

Title:
  Systemd does not send SIGTERM first on shutdown

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Vivid:
  Fix Committed
Status in systemd package in Debian:
  Unknown
Status in systemd package in Fedora:
  Unknown

Bug description:
  It has been normal that applications first get the SIGTERM signal
  before SIGKILL on shutdown/reboot in order to successfully finish any
  pending tasks. Now it seem this logic has been changed to something
  else, causing problems to mosh and many others:

  https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982

  SIGTERM  suggestion can be seen here:

  http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8

  I created this error report to find out the correct way for
  applications to fix this problem or to create one fix to systemd,
  bringing back the old BSD shutdown functionality.

  This report is for Ubuntu 15.04.

  SRU TEST CASE:
   - Open a terminal, enter some commands, then run reboot.
   - After a reboot, chances are very high that your bash history does not 
contain your most recently typed commands
   - With the updated package, the bash history should be intact.

  REGRESSION POTENTIAL:
   - The original commit was applied because of an inherent race condition with 
cgroup's release_agent -- in rare corner cases an nspawn container (probably 
also LXC) can miss them. In that case it's possible that you instead get a 90s 
timeout on the unit that is shutting down. But this does not mean data loss, 
just a rare shutdown hang from containers (for the record, I never actually saw 
that hanging with LXC), so I think it's a good trade-off.

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

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

[Touch-packages] [Bug 1442583] Re: network-manager 0.9.8.8 randomly roames to (none) none

[Axel G. Rossberg]

Update: Did not have the problem recently, so perhaps it's fixed
already.

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

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

Title:
  network-manager 0.9.8.8 randomly roames to (none) none

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  For a description of the problem, and a probable fix in the transition
  from version 0.9.10.0-2 to 0.9.10.0-2.1, please see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732391

  It would be nice if the patch could be merged into Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 10 11:52:45 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-01 (616 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to trusty on 2014-05-25 (320 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 805087] Re: Dash and launcher appear underneath windows

[Axel Pospischil]

Hi there,

this bug drives me crazy since I use Ubuntu 14.04. Due to the fact, that
I am using VirtualBox for developping and Remmina (for RDP sessions to
my business) this gives me from time to time an unaccessible system.

I then have to login remotely an setdid unity or compiz --replace.

Why is this essential algo so problematic? -  A windows other than dash
has the focus = close dash ... ???

Greets Axel

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

Title:
  Dash and launcher appear underneath windows

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Oneiric:
  Fix Released

Bug description:
  main problem:
    unity launcher and dash always hidden (behind displayed application-windows)

  more details and symptoms:
    docky behaves like unity-launcher/dash.
    press super button and type terminal+enter (nothing displayed) ... a 
terminal-window starts/pop-up

  conclusion:
    the input-stack/focus is o.k.
    the windows-display-stack/focus is wrong

  more symptoms:
    After docky-stop and docky-start (restart) the docky-bar shows as 
top-level-window = o.k.
    This is reproducable with firefox windows by moving/maximise/move to 
desktop XY.
    Sometimes other windows (like terminal-window/google-chrome-window) are 
hiding the launcher/dash/docky too.
    This problem is reproducable on a T60p with ATI-FireGL video-card.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.16-0ubuntu1~natty1
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Sun Jul  3 13:58:33 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  DkmsStatus:
   tp-smapi, 0.40, 2.6.38-10-generic, x86_64: installed
   tp-smapi, 0.40, 2.6.38-8-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21d1]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MachineType: LENOVO 428449G
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic 
root=UUID=be0937c9-8117-4833-a50b-1b5c391c9b69 ro quiet splash 
i915.semaphores=1 vt.handoff=7
  ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  ProcVersionSignature__: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Renderer: Unknown
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 04/19/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET42WW (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 428449G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET42WW(1.22):bd04/19/2011:svnLENOVO:pn428449G:pvrThinkPadW520:rvnLENOVO:rn428449G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 428449G
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2
  version.ia32-libs: ia32-libs 20090808ubuntu13
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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

[Touch-packages] [Bug 1416215] [NEW] package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1

[Axel Andres Valderrama Valderrama]

Public bug reported:

Trying to install some libbs, this error apears... i guess that is
because this is a 32x system and those libb use a 64x sudo, so that.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: sudo 1.8.9p5-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Thu Jan 29 13:18:02 2015
DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1:el subproceso instalado el 
script pre-removal devolvió el código de salida de error 1
ErrorMessage: el subproceso instalado el script pre-removal devolvió el código 
de salida de error 1
InstallationDate: Installed on 2015-01-22 (7 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
SourcePackage: sudo
Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso 
instalado el script pre-removal devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers análisis OK
 /etc/sudoers.d/README análisis OK

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


** Tags: amd64 apport-package trusty

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

Title:
  package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso
  instalado el script pre-removal devolvió el código de salida de error
  1

Status in sudo package in Ubuntu:
  New

Bug description:
  Trying to install some libbs, this error apears... i guess that is
  because this is a 32x system and those libb use a 64x sudo, so that.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: sudo 1.8.9p5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Thu Jan 29 13:18:02 2015
  DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1:el subproceso instalado el 
script pre-removal devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script pre-removal devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-01-22 (7 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: sudo
  Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso 
instalado el script pre-removal devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1329939] Re: Service ssh stop/start/restart hangs

[Axel]

] defunct
root 22789 11633  0 Jul26 ?00:00:00 [sshd] defunct
root 22840 11633  0 Jul26 ?00:00:00 [sshd] defunct
root 22842 11633  0 Jul26 ?00:00:00 [sshd] defunct
root 22844 11633  0 Jul26 ?00:00:00 [sshd] defunct
root 23925 11633  0 Jul26 ?00:00:00 [sshd] defunct
root 23927 11633  0 Jul26 ?00:00:00 [sshd] defunct
root 23929 11633  0 Jul26 ?00:00:00 [sshd] defunct
root 23977 11633  0 Jul26 ?00:00:00 [sshd] defunct
root 24773 11633  0 Jul26 ?00:00:00 [sshd] defunct
 removed my logins (4 lines) 
root 26928 11633  0 04:43 ?00:00:00 [sshd] defunct


the sshd config is the default ubuntu config file.
I just added these lines:


Banner /etc/ssh/sshd_banner.txt
PermitRootLogin no
MaxAuthTries 5
LoginGraceTime 1m
UsePAM yes


applied all updates yesterday.

what's going in here???

thanx
 axel

** Information type changed from Public to Private Security

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

Title:
  Service ssh stop/start/restart hangs

Status in “openssh” package in Ubuntu:
  Confirmed

Bug description:
  When using service ssh, all of the actions cause the service process
  to hang, with varying results on the sshd process.

  root@localdev14:~# ps -ef | grep ssh
  root 28264 1  0 15:39 ?00:00:00 /usr/sbin/sshd -D
  root 28353 28264  0 15:46 ?00:00:00 sshd: user [priv]
  user  28402 28353  0 15:46 ?00:00:00 sshd: user@pts/0 
  root 28433 28418  0 15:47 pts/000:00:00 grep --color=auto ssh
  root@localdev14:~# service ssh stop
  (after a couple of minutes)
  ^C
  root@localdev14:~# ps -ef | grep ssh
  root 28264 1  0 15:39 ?00:00:00 /usr/sbin/sshd -D
  root 28353 28264  0 15:46 ?00:00:00 sshd: user [priv]
  user  28402 28353  0 15:46 ?00:00:00 sshd: user@pts/0 
  root 28444 28418  0 15:48 pts/000:00:00 grep --color=auto ssh

  A trace on /usr/sbin/service shows that it's hanging at /sbin/stop;

  root@localdev14:~# bash -x /usr/sbin/service ssh stop 21 | tee 
/tmp/ssh.restart
  ++ basename /usr/sbin/service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename /usr/sbin/service
  + USAGE='Usage: service  option  | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case ${1} in
  + '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
  + '[' 2 -eq 2 -a stop = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=ssh
  + shift
  + '[' 1 -gt 0 ']'
  + case ${1} in
  + '[' -z ssh -a 1 -eq 1 -a stop = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z ssh ']'
  + '[' -z '' ']'
  + ACTION=stop
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/ssh.conf ']'
  + which initctl
  + initctl version
  + grep -q upstart
  + case ${ACTION} in
  + exec stop ssh
  ^C
  root@localdev14:~# ps -ef | grep sshd
  root 28264 1  0 15:39 ?00:00:00 /usr/sbin/sshd -D
  root 28353 28264  0 15:46 ?00:00:00 sshd: user [priv]
  user  28402 28353  0 15:46 ?00:00:00 sshd: user@pts/0 
  root 28478 28418  0 15:54 pts/000:00:00 grep --color=auto sshd

  Restarting the service gets a different error;

  root@localdev14:~# bash -x /usr/sbin/service ssh restart 21 | tee 
/tmp/ssh.restart
  ++ basename /usr/sbin/service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename /usr/sbin/service
  + USAGE='Usage: service  option  | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case ${1} in
  + '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=ssh
  + shift
  + '[' 1 -gt 0 ']'
  + case ${1} in
  + '[' -z ssh -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z ssh ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/ssh.conf ']'
  + which initctl
  + initctl version
  + grep -q upstart
  + case ${ACTION} in
  + stop ssh
  stop: Job has already been stopped: ssh
  + :
  + exec start ssh
  ^C
  root@localdev14:~# ps -ef | grep sshd
  root 28264 1  0 15:39 ?00:00:00 /usr/sbin/sshd -D
  root 28353 28264  0 15:46 ?00:00:00 sshd: user [priv]
  user  28402 28353  0 15:46 ?00:00:00 sshd: user@pts/0 
  root 28495 28418  0 15:56 pts/000:00:00 grep --color=auto sshd

  As you can see from the PID, the sshd service was in fact not stopped.

  If you kill the sshd manually, and try to use the service command to
  start the process, that hangs as well, although

[Touch-packages] [Bug 1329939] Re: Service ssh stop/start/restart hangs

[Axel]

Hi,

I have quite the same problem.
Only after a reboot the sshd is running, working and accepting connections.

Whatever I try:
 stop ssh, 
 restart ssh, 
 start ssh
or with service like:
 service ssh stop/start/restart
or with /etc/init.d/ssh, which isn't doing anything.


the daemon ist (maybe) started, but NOT accepting connections.

the command: start ssh 
does NOT return. and ssh ist not started/running.
I have to press ^C, then the the service is started!  wtf?!?!
and shows up with:/usr/sbin/sshd -D

but in this state it is not accepting connections.
I tries all combinations and methods. 
nothing is working.

funny thing:
when i start it with:   start ssh 
the command returns, nothing is really started  (ps -ef shows nothing)

BUT when i say:   service ssh status

this happens:
ssh start/running, process 11633
ssh start/running, process 11633
[1]+  Donestart ssh

now sshd ist started AND accepting connections!
this really is a bug!
its the only way to start/restart the daemon without reboot :(


best regards
 axel

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

Title:
  Service ssh stop/start/restart hangs

Status in “openssh” package in Ubuntu:
  Confirmed

Bug description:
  When using service ssh, all of the actions cause the service process
  to hang, with varying results on the sshd process.

  root@localdev14:~# ps -ef | grep ssh
  root 28264 1  0 15:39 ?00:00:00 /usr/sbin/sshd -D
  root 28353 28264  0 15:46 ?00:00:00 sshd: user [priv]
  user  28402 28353  0 15:46 ?00:00:00 sshd: user@pts/0 
  root 28433 28418  0 15:47 pts/000:00:00 grep --color=auto ssh
  root@localdev14:~# service ssh stop
  (after a couple of minutes)
  ^C
  root@localdev14:~# ps -ef | grep ssh
  root 28264 1  0 15:39 ?00:00:00 /usr/sbin/sshd -D
  root 28353 28264  0 15:46 ?00:00:00 sshd: user [priv]
  user  28402 28353  0 15:46 ?00:00:00 sshd: user@pts/0 
  root 28444 28418  0 15:48 pts/000:00:00 grep --color=auto ssh

  A trace on /usr/sbin/service shows that it's hanging at /sbin/stop;

  root@localdev14:~# bash -x /usr/sbin/service ssh stop 21 | tee 
/tmp/ssh.restart
  ++ basename /usr/sbin/service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename /usr/sbin/service
  + USAGE='Usage: service  option  | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case ${1} in
  + '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
  + '[' 2 -eq 2 -a stop = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=ssh
  + shift
  + '[' 1 -gt 0 ']'
  + case ${1} in
  + '[' -z ssh -a 1 -eq 1 -a stop = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z ssh ']'
  + '[' -z '' ']'
  + ACTION=stop
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/ssh.conf ']'
  + which initctl
  + initctl version
  + grep -q upstart
  + case ${ACTION} in
  + exec stop ssh
  ^C
  root@localdev14:~# ps -ef | grep sshd
  root 28264 1  0 15:39 ?00:00:00 /usr/sbin/sshd -D
  root 28353 28264  0 15:46 ?00:00:00 sshd: user [priv]
  user  28402 28353  0 15:46 ?00:00:00 sshd: user@pts/0 
  root 28478 28418  0 15:54 pts/000:00:00 grep --color=auto sshd

  Restarting the service gets a different error;

  root@localdev14:~# bash -x /usr/sbin/service ssh restart 21 | tee 
/tmp/ssh.restart
  ++ basename /usr/sbin/service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename /usr/sbin/service
  + USAGE='Usage: service  option  | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case ${1} in
  + '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=ssh
  + shift
  + '[' 1 -gt 0 ']'
  + case ${1} in
  + '[' -z ssh -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z ssh ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/ssh.conf ']'
  + which initctl
  + initctl version
  + grep -q upstart
  + case ${ACTION} in
  + stop ssh
  stop: Job has already been stopped: ssh
  + :
  + exec start ssh
  ^C
  root@localdev14:~# ps -ef | grep sshd
  root 28264 1  0 15:39 ?00:00:00 /usr/sbin/sshd -D
  root 28353 28264  0 15:46 ?00:00:00 sshd: user [priv]
  user  28402 28353  0 15:46 ?00:00:00 sshd: user@pts/0 
  root 28495 28418  0 15:56 pts/000:00:00 grep --color=auto sshd

  As you can see from the PID, the sshd service was in fact not stopped.

  If you kill the sshd manually, and try