[Touch-packages] [Bug 1622206] Re: package account-plugin-google not installed failed to install/upgrade: trying to overwrite /usr/share/accounts/services/google-im.service , which is also in package

[Martin Weis]

Ran into the same issue, and was stuck with apt not being able to get to
a working, clean state, see below.

I had to use aptitude (instead of apt), which gave a proper solution and 
managed to deinstall, finally my solution was:
aptitude remove kde-telepathy-minimal
apt remove 'unity-*'
apt autoremove
apt remove kubuntu-desktop
apt install --reinstall kubuntu-desktop


# apt remove unity
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies... Done
The following additional packages will be installed:
  kde-config-telepathy-accounts
The following NEW packages will be installed:
  kde-config-telepathy-accounts
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
385 not fully installed or removed.
Need to get 0 B/137 kB of archives.
After this operation, 825 kB of additional disk space will be used.
(Reading database ... 55%[Y/n] (Reading database ... 
(Reading database ... 759436 files and directories currently installed.)
Preparing to unpack 
.../kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb ..
.
Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%
3a15.12.3-0ubuntu1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/accounts/services/google-im.service', which is 
also in
 package account-plugin-google 0.12+16.04.20160126-0ubuntu1
Processing triggers for libc-bin (2.23-0ubuntu7) ...
Errors were encountered while processing:
 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

# aptitude why account-plugin-google
i   unity  Empfiehltunity-scope-gdrive   
i A unity-scope-gdrive Hängt ab von account-plugin-google

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

Title:
  package account-plugin-google  not installed  failed to
  install/upgrade: trying to overwrite  /usr/share/accounts/services
  /google-im.service , which is also in package kde-config-telepathy-
  accounts 4:15.12.3-0ubuntu1!

Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep 10 00:41:19 2016
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-09-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1622206/+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 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[Brian]

@James- Thanks for all the help. I went through the steps and in the
end, nothing was any different. I was at least able to learn some of the
steps used here which I really appreciate. I did not see anything too
unusual... there was an error on not being able to sign in the end and
many warnings throughout (ex. depreciated items, defined but not used
variables, etc), but the build did finish and I was able to verify that
the patch applied to the proper file. My guess is either something was
not right or my experience is just too limited resulting in user error
somewhere.

Let me know if and when there are any other options. Thanks again, I
really do appreciate what I have learned in the process with your
direction.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/abiword/+bug/1574278/+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 1688689] Re: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container

[Bug Watch Updater]

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

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

Title:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup within nspawn container

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

Bug description:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup when I check permission from within nspawn
  container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders and files in Bind directory inside container is the 
same as on host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1688689/+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 1641328] Re: Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS lookups to fail -- breaks network printing

[Mark Tearle]

Just did a quick test with a clean install of zesty + libnss-mdns

Installs with a correct ordering of resolvers in /etc/nsswitch.conf and
works correctly.

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

Title:
  Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes
  mDNS lookups to fail -- breaks network printing

Status in nss-mdns package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  (See also libnss-resolve:amd64   231-9ubuntu1 amd64nss module
  to resolve names via systemd-resolved)

  
  # fresh install of yakkety 

  mtearle@liberation:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  # package details

  mtearle@liberation:~$ apt-cache policy libnss-resolve
  libnss-resolve:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
   *** 231-9ubuntu1 500
  500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages
  mtearle@liberation:~$ apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
   *** 231-9ubuntu1 500
  500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages



  # attempt to ping VM elsewhere on network with mDNS hostname

  mtearle@liberation:/etc$ ping bazzavan.local
  ping: bazzavan.local: Name or service not known

  # can find both ipv4 and ipv6 addresses for the host

  mtearle@liberation:/etc$ avahi-resolve-host-name bazzavan.local
  bazzavan.localfe80::a00:27ff:fea5:3f51

  mtearle@liberation:/etc$ avahi-resolve-host-name -4 bazzavan.local
  bazzavan.local172.16.44.48

  # can ping it

  mtearle@liberation:/etc$ ping -c 1 172.16.44.48
  PING 172.16.44.48 (172.16.44.48) 56(84) bytes of data.
  64 bytes from 172.16.44.48: icmp_seq=1 ttl=64 time=0.265 ms

  --- 172.16.44.48 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.265/0.265/0.265/0.000 ms

  # original ordering

  mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf 
  hosts:  files resolve [!UNAVAIL=return] mdns4_minimal 
[NOTFOUND=return] dns

  # go away and edit /etc/nsswitch.conf
  # change ordering of resolve and mdns4_minimal

  mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf 
  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns

  # check mdns lookups now work, and it now pings

  mtearle@liberation:/etc$ ping -c 1 bazzavan.local
  PING bazzavan.local (172.16.44.48) 56(84) bytes of data.
  64 bytes from 172.16.44.48 (172.16.44.48): icmp_seq=1 ttl=64 time=0.161 ms

  --- bazzavan.local ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.161/0.161/0.161/0.000 ms

  
  # check libnss-resolve is still doing its thing

  mtearle@liberation:/etc$ ping -c 1 localhost.localdomain
  PING localhost.localdomain(localhost (::1%1)) 56 data bytes
  64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.016 ms

  --- localhost.localdomain ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.016/0.016/0.016/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1641328/+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 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[James Cameron]

G'day Brian. Good to hear. For local testing, the signing can be
ignored; there's an option to skip it. The warnings sound familiar,
but are normal. For me, the patch did fix the flickering of the whole
screen, but did not fix the flickering cursor. Guess next steps
upstream involve reproducing and debugging in depth to find out why
the flickering happens.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/abiword/+bug/1574278/+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 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[Henk Terhell]

I have experienced that Abiword cannot be used on plain Debian Stretch,
Lubuntu 17.04 and Xubuntu 17.04, all using gtk-3.22. Heavy flickering or
moving of paper borders occurs, which stops, together with disappearing
cursor,  after about 8 seconds without activity. Changing the theme does
not have any effect.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/abiword/+bug/1574278/+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 1687507] Re: Memory leak (/run file system filling up)

[Martin Winter]

Sorry for slow response - I'm still trying to figure out the steps to reproduce 
this reliable.
It does happen when I use my snap in the CI system (installing, testing, 
removing).

It happens reliable with my CI system testing my snap (frr) when I do
run it against a commercial protocol compliance suite. Challenge is to
figure out which specific part of the commands executed cause the
problem.

This is seen on Ubuntu 16.04 server (classic). Normally testing with the 
alternative 4.8.0-49
kernel (every other package updated to latest). I'm running the alternative 4.8 
kernel as I need something >= 4.5 for my MPLS networking tests.

At this time it does look like the issue is related to the 4.8 kernel as I'm 
currently not able
to reproduce the same issue with the standard 4.4 kernel (testing 4.4.0-77)

I'll update again in a few days when I've done enough tests to be
certain that it is depending on the kernel.

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

Title:
  Memory leak (/run file system filling up)

Status in snapd:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  (see also related discussion on forum:
  
https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429
 )

  I have a CI system which tests my snap and does a lot install/remove of snap 
packages as part
  of the operation on some small virtual systems. My /tmp is 200MB

  This is on latest Ubuntu Server 16.04 (all packages updated), with the 
alternative 4.8 kernel
  from the Ubuntu Repo)

  At this time, all packages are updated to latest version. I have this bug for 
a long time (since I've started building up a CI infrastructure for the Snap - 
approx 6 months ago), so this is
  not a new bug, but only the more frequent snap testing made it obvious.

  In my system the /tmp filesystem fills up - within approx 2..7 days I'm out 
of space on it.
  All the space is used up under /run/udev/data/  and approx 95% of the files 
(around 45'000)
  start with +cgroup prefix

  I can provide access to a VM in this state if requested (IPv6 only,
  contact me with SSH key)

  Here is some current output (not yet out of space... may need another
  day)

  root@ci-comp17-dut:~# df
  Filesystem 1K-blocksUsed Available Use% Mounted on
  udev 1002892   0   1002892   0% /dev
  tmpfs 204796  148196 56600  73% /run
  /dev/vda16060608 3462628   2267076  61% /
  tmpfs1023976   0   1023976   0% /dev/shm
  tmpfs   5120   0  5120   0% /run/lock
  tmpfs1023976   0   1023976   0% /sys/fs/cgroup
  /dev/loop0 80256   80256 0 100% /snap/core/1577
  /dev/loop1 77056   77056 0 100% /snap/core/1337
  /dev/loop2 80256   80256 0 100% /snap/core/1441
  tmpfs 204796   0204796   0% /run/user/0
  /dev/loop3 14592   14592 0 100% /snap/frr/x1

  Attached is a full dir output of /run/udev/data
  (ls_run_udev_data.log)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1687507/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[cl-netbox]

I added more information to the existing bug report :
https://bugzilla.gnome.org/show_bug.cgi?id=782191#c1

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

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

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

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in gnome-online-accounts source package in Xenial:
  Triaged
Status in gnome-online-accounts source package in Yakkety:
  Triaged
Status in gnome-online-accounts source package in Zesty:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+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 1595695] Re: bluetooth indicator disappears every time bluetooth is being turned off

[leo]

Please solve this this is very anoying !


** Attachment added: "Picture of what I would like to see but insted the icon 
desapears"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1595695/+attachment/4872532/+files/Screenshot%20from%202017-05-06%2012-28-21.png

** Summary changed:

- bluetooth indicator disappears every time bluetooth is being turned off
+ Bluetooth indicator disappears every time bluetooth is being turned off

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

Title:
  Bluetooth indicator disappears every time bluetooth is being turned
  off

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon 
disappears from the top panel.
  Each time I have to re-enable it by system setting or via dash.

  I expect it to behave in a same way as network indicator instead of
  disappearing.

  Here is the link with some info which could be helpful 
  https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1595695/+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 1574278] Re: AbiWord text cursor starts to flicker after adding some text

[Brian]

Maybe I did not mess it up then. I would agree that the warnings I saw
were all non-critical, and it did complete. I am using MATE 17.04 64
bit., gtk 3.22 and is about exactly as Henk explains above. I can also
confirm that changing the theme makes no difference for me, and I
believe now that the patch is not effective either. I was using 16.10
prior to the upgrade and all worked fine.

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in lubuntu-artwork package in Ubuntu:
  Invalid
Status in abiword source package in Xenial:
  Confirmed
Status in gtk+3.0 source package in Xenial:
  Confirmed
Status in lubuntu-artwork source package in Xenial:
  Invalid

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/abiword/+bug/1574278/+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 1126108] Re: Indicator disappears entirely when disabling / turning off bluetooth

[leo]

This bug is (sadly ?) marked as fixed, so if you still have this problem like 
me please say you are affected at:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1595695

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

Title:
  Indicator disappears entirely when disabling / turning off bluetooth

Status in indicator-bluetooth package in Ubuntu:
  Fix Released

Bug description:
  Bug 1116289 made the BT indicator disappear when there is no hardware.
  However, with that version I now also have it disappear when my
  existing BT hardware is merely disabled. I. e. I disable BT from the
  indicator, then it disappears, leaving me no obvious method to turn it
  back on again. I can re-enabble it in control-center, and then the
  indicator comes back.

  I think when it sees no actual BT hardware it ought to check rfkill
  whether there is disabled BT hardware:

  $ grep -r . /sys/class/rfkill/rfkill0/{type,state,soft,persistent}
  /sys/class/rfkill/rfkill0/type:bluetooth
  /sys/class/rfkill/rfkill0/state:1
  /sys/class/rfkill/rfkill0/soft:0
  /sys/class/rfkill/rfkill0/persistent:1

  After disabling BT from the indicator, "soft" changes to 1:

  $ grep -r . /sys/class/rfkill/rfkill0/{type,state,soft,persistent}
  /sys/class/rfkill/rfkill0/type:bluetooth
  /sys/class/rfkill/rfkill0/state:0
  /sys/class/rfkill/rfkill0/soft:1
  /sys/class/rfkill/rfkill0/persistent:1

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-bluetooth 0.0.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 15 12:08:26 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-08 (7 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130207.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108/+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 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off

[leo]

This clearly shows what the problem is. I hope so.

** Attachment added: "Description of the big problem we all have. 
#BluetoothMess. #GimpLove"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1595695/+attachment/4872533/+files/UbuntuBT10.png

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

Title:
  Bluetooth indicator disappears every time bluetooth is being turned
  off

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon 
disappears from the top panel.
  Each time I have to re-enable it by system setting or via dash.

  I expect it to behave in a same way as network indicator instead of
  disappearing.

  Here is the link with some info which could be helpful 
  https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1595695/+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 1271839] Re: ibus-ui-gtk3 big memory leak

[Dennis]

I can confirm that this bug ist still present in Ubuntu Ubuntu 16.04.2 LTS. 
ibus-daemon and ibus-ui-gtk3 allocated together at least 2GB of ram. They also 
caused together approximately 40% CPU load.

** Changed in: ibus (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  ibus-ui-gtk3 big memory leak

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 13.10 64bit
  2gb of memory leak

  Also seen on Ubuntu 14.04 64Bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+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 1688721] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Rafael Belmonte]

Public bug reported:

I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. Other 
times, the installation process just hangs at some percentage. I am testing 
this gnome-software version due to Bug (LP: #1672424).
The same file was successfully installed with gdebi.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
AptOrdering:
 gconf2-common:amd64: Install
 libgconf-2-4:amd64: Install
 gconf-service-backend:amd64: Install
 gconf-service:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat May  6 13:56:26 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-04 (1 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

** Description changed:

  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
- This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug LP:#1672424.
+ This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.
  
  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
-  gconf2-common:amd64: Install
-  libgconf-2-4:amd64: Install
-  gconf-service-backend:amd64: Install
-  gconf-service:amd64: Install
-  NULL: ConfigurePending
+  gconf2-common:amd64: Install
+  libgconf-2-4:amd64: Install
+  gconf-service-backend:amd64: Install
+  gconf-service:amd64: Install
+  NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
-  dpkg 1.18.10ubuntu2
-  apt  1.4
+  dpkg 1.18.10ubuntu2
+  apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script re

[Touch-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1688721/+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 1688725] [NEW] ibus-engine-simple does not terminate at computer shutdown

[Pora Ontor]

Public bug reported:

I cannot upgrade log

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ibus 1.5.11-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sat May  6 18:50:35 2017
ExecutablePath: /usr/lib/ibus/ibus-engine-simple
ExecutableTimestamp: 1453211340
InitctlList: Error: command ['initctl', 'list'] failed with exit code 1: 
initctl: Name "com.ubuntu.Upstart" does not exist
InstallationDate: Installed on 2017-02-14 (80 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: /usr/lib/ibus/ibus-engine-simple
ProcCwd: /home/leon-561
SourcePackage: ibus
Title: ibus-engine-simple does not terminate at computer shutdown
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug shutdown-hang

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

Title:
  ibus-engine-simple does not terminate at computer shutdown

Status in ibus package in Ubuntu:
  New

Bug description:
  I cannot upgrade log

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ibus 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat May  6 18:50:35 2017
  ExecutablePath: /usr/lib/ibus/ibus-engine-simple
  ExecutableTimestamp: 1453211340
  InitctlList: Error: command ['initctl', 'list'] failed with exit code 1: 
initctl: Name "com.ubuntu.Upstart" does not exist
  InstallationDate: Installed on 2017-02-14 (80 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/lib/ibus/ibus-engine-simple
  ProcCwd: /home/leon-561
  SourcePackage: ibus
  Title: ibus-engine-simple does not terminate at computer shutdown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1688725/+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 1215420] Re: [7515A47, Realtek ALC662 rev1, Green Line Out, Rear] Playback problem

[Jeremy Bicha]

** No longer affects: mutter (Ubuntu)

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

Title:
  [7515A47, Realtek ALC662 rev1, Green Line Out, Rear] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It hangs itself often! It is closed only!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic-pae 3.2.48
  Uname: Linux 3.2.0-51-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cyberthrone   2557 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfeaf8000 irq 44'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,17aa304f,00100101'
 Controls  : 29
 Simple ctrls  : 15
  Date: Wed Aug 21 00:47:08 2013
  InstallationMedia: Zorin 6 - Release i386
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Only some of outputs are working
  Title: [7515A47, Realtek ALC662 rev1, Green Line Out, Rear] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5HKT39AUS
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr5HKT39AUS:bd06/17/2009:svnLENOVO:pn7515A47:pvrThinkCentreA58:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 7515A47
  dmi.product.version: ThinkCentre A58
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1215420/+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 1688737] [NEW] Keep getting the aw snap error message when trying to browse

[Tim Moore]

Public bug reported:

Keep getting the "aw snap" error message when trying to browse third party site;
Looking at paper, click to read story, drops website

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat May  6 10:14:39 2017
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DpkgLog:
 
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:027f]
   Subsystem: Dell Device [1028:027f]
InstallationDate: Installed on 2015-05-01 (735 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. OptiPlex 760
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0M863N
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/17/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M863N:rvrA01:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri May  5 16:45:29 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16570 
 vendor DEL
xserver.version: 2:1.15.1-0ubuntu2.7

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


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

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

Title:
  Keep getting the aw snap error message when trying to browse

Status in xorg package in Ubuntu:
  New

Bug description:
  Keep getting the "aw snap" error message when trying to browse third party 
site;
  Looking at paper, click to read story, drops website

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat May  6 10:14:39 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:027f]
 Subsystem: Dell Device [1028:027f]
  InstallationDate: Installed on 2015-05-01 (735 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. OptiPlex 760
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0M863N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/17/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M863N:rvrA01:cvnDellInc.:ct15:cvr:
  dm

[Touch-packages] [Bug 1686544] Re: sudo fails to retrieve groups in sudoUser

[quess]

In the link posted above, the OP solves the problem by adding objectClass: 
posixgroup to his groups.
In my case, they already are "posix-ified".

But, I finally made my sudorules to work by turning
use_fully_qualified_names = False.

Summary:
use_fully_qualified_names = True  + sudo 1.8.16-0ubuntu1   => OK
use_fully_qualified_names = True  + sudo 1.8.16-0ubuntu1.3 => NOK
use_fully_qualified_names = False + sudo 1.8.16-0ubuntu1.3 => OK

Remaining problems:
sudoUser=%#gid is not retrieved

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

Title:
  sudo fails to retrieve groups in sudoUser

Status in sudo package in Ubuntu:
  New

Bug description:
  Currently using sudo with sssd 1.13.4 on xenial to manage sudo rules,
  groups are not resolved since last update.

  I troubleshooted :
  - sudo with all@debug
  - sssd with [sudo] debug_level = 9 and [domain/domain.tld] debug_level = 9
  - LDAP requests are correctly sent, and I can obtain correct rules
  - SSSD cache is correctly stored too, I can successfully ldbsearch into!

  I had to downgrade sudo (1.8.16-0ubuntu1.3) xenial to sudo
  (1.8.16-0ubuntu1) xenial, to get my groups working again. I tried sudo
  1.8.19, with no luck.

  
  Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: ALL

  Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: #uid

  Broken since 1.8.16-0ubuntu1.3:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: %mygroup

  Broken in 1.8.16-0ubuntu1.3:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: myuser

  
  Patch sssd-doesnt-handle-netgroups.diff seems to break something...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1686544/+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 1688747] [NEW] frequent unabity to connect to websites, frequent connection problem.

[David]

Public bug reported:

 Cabled conection to ADSL. frequently unable to connect to websites,
restarting network manager resolves problem temporarily. Seems to be no
problem when connected to VPN. After diconecting VPN connection, not
able to connect to internet. Restart connection or network manager
needed.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sat May  6 16:53:50 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-01-21 (105 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IpRoute:
 default via 192.168.1.1 dev enp4s1 proto static metric 100 
 169.254.0.0/16 dev enp4s1 scope link metric 1000 
 192.168.1.0/24 dev enp4s1 proto kernel scope link src 192.168.1.3 metric 100
IwConfig:
 lono wireless extensions.
 
 enp4s1no wireless extensions.
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-15 (21 days ago)
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp4s1  ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
Connessione via cavo 1  e6fa8c59-3af2-3ef5-9425-38f3b0ed6c60  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  frequent unabity to connect to websites, frequent connection problem.

Status in network-manager package in Ubuntu:
  New

Bug description:
   Cabled conection to ADSL. frequently unable to connect to websites,
  restarting network manager resolves problem temporarily. Seems to be
  no problem when connected to VPN. After diconecting VPN connection,
  not able to connect to internet. Restart connection or network manager
  needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat May  6 16:53:50 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-21 (105 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev enp4s1 proto static metric 100 
   169.254.0.0/16 dev enp4s1 scope link metric 1000 
   192.168.1.0/24 dev enp4s1 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp4s1no wireless extensions.
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (21 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp4s1  ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
Connessione via cavo 1  e6fa8c59-3af2-3ef5-9425-38f3b0ed6c60  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1654832] Re: Network manager shows virtual vmnet interfaces

[Launchpad Bug Tracker]

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

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

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

Title:
  Network manager shows virtual vmnet interfaces

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  Kernel: 4.4.0-57-generic(x86_64)

  network-manager-gnome v. 1.2.0
  network-manager v. 1.2.2

  
  I have just installed Ubuntu 16.04 and I have noticed that virtual interfaces 
created by vmware player such as vmnet1 and vmnet8 are shown in the nm-applet 
as not managed deviced and recognized as Ethernet connection. Is that behaviour 
expected? It was not the case for Ubuntu 14.04.

  nmcli dev
  DEVICE  TIPO  STATOCONNESSIONE 
  wlo1wifi  collegatoN2O2
  eno1ethernet  non disponibile  --  
  vmnet1  ethernet  non gestito  --  
  vmnet8  ethernet  non gestito  --  
  lo  loopback  non gestito  --

  So far I did not find a way to hide them. Moreover the full name of
  the pci card is also shown for the real ethernet interface eno1:

  Rete Ethernet(RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller) 
  disconnessi

  making the pop-up window very large

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1654832/+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 1461834] Re: 1024-bit signing keys should be deprecated

[Bob Freeman]

** Tags added: encryption needs-update security vulnerability

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

Title:
  1024-bit signing keys should be deprecated

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  1024-bit RSA was deprecated  years ago by NIST[1], Microsoft[2] and
  more recently by others[3].

  1024-bit signing keys are insufficient to guarantee the authenticity
  of software distributed from Launchpad.net including PPAs. There
  should be a mechanism to refuse signing keys below a minimum key
  length based on key type. 1024-bit signing keys should be deprecated
  and removed from Launchpad.net itself ASAP.  Future projects and PPAs
  should be disallowed from using 1024-bit signing keys.

  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1461834/+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 1558899] Re: Recent recipe version of FreeFont were failed to build

[Adolfo Jayme]

Bug reports like this one, filed against the Ubuntu project, are
inappropriate for PPA-originated packages. Only file bugs here if your
bug is related to packages from the Ubuntu archive.

I suggest you contact user ~dns, who is the maintainer of that PPA.

** Changed in: fonts-freefont (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Recent recipe version of FreeFont were failed to build

Status in fonts-freefont package in Ubuntu:
  New

Bug description:
  Since 2016-03-16, recipe builds of FreeFont were failed to build when I try 
to download from here:
  https://code.launchpad.net/~dns/+recipe/freefont

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1558899/+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 1461834] Re: 1024-bit signing keys should be deprecated

[Bob Freeman]

Updates usually run automatically in the background, including from
PPAs, and are unencrypted. This means a man-in-the-middle can gain root
access, just by inserting their own version of one of the packages into
this network traffic, because updates run as root. They can first obtain
the public 1024 bit key from the PPA, then spend as long as they want
working out the private key, then sign their false updates with the real
private key.

A bug that allows complete compromise of most Ubuntu machines without
requiring any user involvement is a very serious bug. Why hasn't this
even been assigned to anyone, nearly 2 years after it was reported?

This makes many PPAs unusable.

https://en.wikipedia.org/wiki/Key_size#Asymmetric_algorithm_key_lengths
'RSA claims that 1024-bit keys are likely to become crackable some time between 
2006 and 2010'
https://www.symantec.com/page.jsp?id=1024-bit-migration-faq#issue
In compliance with Certification Authority/Browser forum requirements based on 
NIST Special Publication 800-131A, at the end of 2013 all web browsers and 
Certification Authorities (CAs) will no longer sell or support 1024-bit RSA 
certificates. All certificates less than 2048-bit key length will need to be 
revoked and replaced with certificates with a higher encryption strength. 

Network connections are secured with at least 2048 bits. Installing
software allows root access and should probably be secured with at least
4096 bits.

Any system using keys has to have a way to change to a new key, that's a basic 
requirement.
You could force all 1024 bit keys to 4096 bits - this might break existing 
updates, but they are already 'broken' by being vulnerable. Or sign with 2 
keys, so a new subscriber will only use the newer one, but old subscribers who 
don't do anything about it will still use the old key. Or re-issue the entire 
PPA namespace, ie ppa2:... Or do some other such thing, eg update the client to 
include a newer protocol version number in its requests.

A simple workaround for launchpad to apply would be to change the urls
in files in /etc/apt/sources.list.d/ to use https://ppa.launchpad.net/
instead of http://ppa.launchpad.net/ (and change the server to support
it). This would only need to be done for any PPA still using a 1024 bit
key. Then at least the packages would be authenticated by TLS, which
already uses 2048 bit keys.

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

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

Title:
  1024-bit signing keys should be deprecated

Status in Launchpad itself:
  New
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  1024-bit RSA was deprecated  years ago by NIST[1], Microsoft[2] and
  more recently by others[3].

  1024-bit signing keys are insufficient to guarantee the authenticity
  of software distributed from Launchpad.net including PPAs. There
  should be a mechanism to refuse signing keys below a minimum key
  length based on key type. 1024-bit signing keys should be deprecated
  and removed from Launchpad.net itself ASAP.  Future projects and PPAs
  should be disallowed from using 1024-bit signing keys.

  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1461834/+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 1688737] Re: Keep getting the aw snap error message when trying to browse

[Timo Aaltonen]

has nothing to do with xorg

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

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

Title:
  Keep getting the aw snap error message when trying to browse

Status in Ubuntu:
  New

Bug description:
  Keep getting the "aw snap" error message when trying to browse third party 
site;
  Looking at paper, click to read story, drops website

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat May  6 10:14:39 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:027f]
 Subsystem: Dell Device [1028:027f]
  InstallationDate: Installed on 2015-05-01 (735 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. OptiPlex 760
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0M863N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/17/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M863N:rvrA01:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 760
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri May  5 16:45:29 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16570 
   vendor DEL
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1688737/+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 1461834] Re: 1024-bit signing keys should be deprecated

[Bob Freeman]

Launchpad could *automatically* create a mirror of any PPA that still
uses a 1024 bit key, with a standard suffix to the name, eg xyzppa gets
mirrored as xyzppa-newkey. It could then link to it from the page for
the original PPA. It would always have all the same source, built files
and other content, and the content would only need to be stored once on
the server. It would just be a different way of accessing the same PPA.

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

Title:
  1024-bit signing keys should be deprecated

Status in Launchpad itself:
  New
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  1024-bit RSA was deprecated  years ago by NIST[1], Microsoft[2] and
  more recently by others[3].

  1024-bit signing keys are insufficient to guarantee the authenticity
  of software distributed from Launchpad.net including PPAs. There
  should be a mechanism to refuse signing keys below a minimum key
  length based on key type. 1024-bit signing keys should be deprecated
  and removed from Launchpad.net itself ASAP.  Future projects and PPAs
  should be disallowed from using 1024-bit signing keys.

  1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
  2. 
http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx
  3. 
https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1461834/+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 1688757] [NEW] systemd-resolved would retry DNSSEC after some time.

[allfox_wy]

Public bug reported:

Greetings everyone.

I know that recently systemd-resolved switched DNSSEC to off by default. 
However, there is a "feature set test" function in it. I could see these in my 
log:
 62 May  6 23:27:31 lavender systemd-resolved[1127]: Grace period over, 
resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 10.2.5.7.
 63 May  6 23:27:31 lavender systemd-resolved[1127]: Using degraded feature set 
(UDP) for DNS server 10.2.5.7.

It looks like this "feature set test" would repeat after some time. And
during the test, it would test DNSSEC again regardless it turned off
explicitly, which is the so called "DO" test.

I could still sometimes get no DNS, and I caught these log once during
that. I can't be sure that this test is connected to my losing DNS, as I
only caught it once. I don't know how long the "grace period" is, so
can't schedule a trap to catch more.

This "DO" test can not be disabled via configuration.

There is an upstream patch to deal with it:
https://github.com/systemd/systemd/issues/5352

While I'm not sure if it does cause some problem, I'm thinking it might
be worth to cherry pick the patch.


Additional info about my system:
lsb_release -rd:
Description:Ubuntu 17.04
Release:17.04

It's Ubuntu GNOME.

Package: systemd
Version: 232-21ubuntu3

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


** Tags: dns dnssec systemd-resolved

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

Title:
  systemd-resolved would retry DNSSEC after some time.

Status in systemd package in Ubuntu:
  New

Bug description:
  Greetings everyone.

  I know that recently systemd-resolved switched DNSSEC to off by default. 
However, there is a "feature set test" function in it. I could see these in my 
log:
   62 May  6 23:27:31 lavender systemd-resolved[1127]: Grace period over, 
resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 10.2.5.7.
   63 May  6 23:27:31 lavender systemd-resolved[1127]: Using degraded feature 
set (UDP) for DNS server 10.2.5.7.

  It looks like this "feature set test" would repeat after some time.
  And during the test, it would test DNSSEC again regardless it turned
  off explicitly, which is the so called "DO" test.

  I could still sometimes get no DNS, and I caught these log once during
  that. I can't be sure that this test is connected to my losing DNS, as
  I only caught it once. I don't know how long the "grace period" is, so
  can't schedule a trap to catch more.

  This "DO" test can not be disabled via configuration.

  There is an upstream patch to deal with it:
  https://github.com/systemd/systemd/issues/5352

  While I'm not sure if it does cause some problem, I'm thinking it
  might be worth to cherry pick the patch.

  
  Additional info about my system:
  lsb_release -rd:
  Description:  Ubuntu 17.04
  Release:  17.04

  It's Ubuntu GNOME.

  Package: systemd
  Version: 232-21ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1688757/+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 1671611] Re: USB wi-fi dongles not working with latest updates

[Antoine W]

At the time of my last comment (2017-04-20), it was already working well
in Xubuntu 16.04, it is still not working in Xubuntu 17.04, i have to
use wicd instead for the moment.

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

Title:
  USB wi-fi dongles not working with latest updates

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

Bug description:
  Same laptop - two different network dongles (ASUS USB-N13 + Edimax
  cheap commonly used with RaspPis). Confirmed issue with xenial-updates
  and xenial-security versions. Going to try to force a downgrade to
  original xenial to see if it still happens.

  ASUS dongle -> $ inxi -Fxxrzc0 | pastebin
  https://gist.github.com/d926d05c2bd23226a9f4b4a593b9de65

  Edimax dongle -> $ inxi -Fxxrzc0 | pastebin
  https://gist.github.com/f76284151c225ae43af82de8439efe02

  
  They work fine w/ the 18.1 Installer/Live Boot.. They worked fine after the 
install.. when I did the latest update they broke. 

  uname -a ->  Linux thinkpad 4.8.0-41-generic #44~16.04.1-Ubuntu SMP
  Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  Description:  Linux Mint 18.1 Serena
  Release:  18.1

  kern.log paste:

  
  Mar  9 12:11:17 thinkpad kernel: [  244.854264] usb 1-2: USB disconnect, 
device number 4
  Mar  9 12:11:17 thinkpad kernel: [  244.864634] wlx2c4d5406c9c1: 
deauthenticating from 58:6d:8f:8e:02:5d by local choice (Reason: 
3=DEAUTH_LEAVING)
  Mar  9 12:11:17 thinkpad kernel: [  244.864846] rtl_usb: reg 0x102, 
usbctrl_vendorreq TimeOut! status:0xffed value=0xf00069ce
  Mar  9 12:11:17 thinkpad kernel: [  244.864858] rtl_usb: reg 0x422, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424
  Mar  9 12:11:17 thinkpad kernel: [  244.864866] rtl_usb: reg 0x542, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424
  Mar  9 12:11:17 thinkpad kernel: [  244.864879] rtl_usb: reg 0x1cc, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x1950812
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3310] 
sup-iface[0xa2d380,wlx2c4d5406c9c1]: connection disconnected (reason -3)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3318] 
device (wlx2c4d5406c9c1): state change: activated -> unmanaged (reason 
'removed') [100 10 36]
  Mar  9 12:11:17 thinkpad kernel: [  244.899266] cfg80211: World regulatory 
domain updated:
  Mar  9 12:11:17 thinkpad kernel: [  244.899273] cfg80211:  DFS Master region: 
unset
  Mar  9 12:11:17 thinkpad kernel: [  244.899275] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Mar  9 12:11:17 thinkpad kernel: [  244.899280] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899283] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899286] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899290] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899295] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Mar  9 12:11:17 thinkpad kernel: [  244.899298] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Mar  9 12:11:17 thinkpad kernel: [  244.899301] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899304] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3642] dhcp4 
(wlx2c4d5406c9c1): canceled DHCP transaction, DHCP client pid 2225
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3643] dhcp4 
(wlx2c4d5406c9c1): state changed bound -> done
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3703] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3705] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3708] 
dns-mgr: Writing DNS information to /sbin/resolvconf
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3879] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3879] 
device (wlx2c4d5406c9c1): failed to disable userspace IPv6LL address handling
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3880] radio 
killswitch 
/sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/ieee80211/phy0/r

[Touch-packages] [Bug 1688759] [NEW] package wswiss 20151222-1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[srinivasansasikumar]

Public bug reported:

hdd was hotter during this error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: wswiss 20151222-1
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
Date: Sat May  6 22:17:09 2017
ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: igerman98
Title: package wswiss 20151222-1 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package wswiss 20151222-1 failed to install/upgrade: subprocess
  installed post-removal script returned error exit status 1

Status in igerman98 package in Ubuntu:
  New

Bug description:
  hdd was hotter during this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: wswiss 20151222-1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  Date: Sat May  6 22:17:09 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: igerman98
  Title: package wswiss 20151222-1 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/igerman98/+bug/1688759/+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 1654918] Re: No Internet access with default of Automatic (DHCP)

[Pedro Jimenez]

I updated my Ubuntu from 16.10 to 17.04 and the network work as
expected.

But then I made a fresh install of both systems (Ubuntu 17.04 and Ubuntu
Gnome 17.04) and I couldn't connect to the wifi anymore.

However the solution that Doug McMahon on the comment #14 works for me.

Thanks for the fix.

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

Title:
  No Internet access with default of  Automatic (DHCP)

Status in Linux:
  Invalid
Status in NetworkManager:
  Invalid
Status in systemd:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there is 
no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & 
manually add Google DNS nameservers: then internet is enabled. screen attached
  Note this also affects ethernet, not just wireless
  Hardware is:
  description: Wireless interface
     product: Wireless 7260
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:08:00.0
     logical name: wlp8s0
     version: 73
     serial: 
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 
link=ye s multicast=yes wireless=IEEE 802.11
     resources: irq:32 memory:c240-c2401fff

  To note: this hardware works perfectly in 14.04 > 16.04
  Add. note; issue doesn't arise with 4.11.x kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  8 22:08:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0  proto static  metric 600
   169.254.0.0/16 dev wlp8s0  scope link  metric 1000
   192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4  metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+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 1651623] Re: adt tests fail on zesty for apport

[Dimitri John Ledkov]

I did notice that, but did not dig into that failure, as I wanted to only
fix the gpg stuff.

On 6 May 2017 at 00:16, Brian Murray  wrote:

> The tests for artful are now failing for a different reason:
>
> ==
> ERROR: test_add_gdb_info_abort_glib (__main__.T)
> add_gdb_info() with glib assertion
> --
> Traceback (most recent call last):
>   File "./test_report.py", line 852, in test_add_gdb_info_abort_glib
> self.assertTrue(pr['AssertionMessage'].startswith('ERROR::2:main:
> assertion failed (1 < 0):'),
>   File "/usr/lib/python3.5/collections/__init__.py", line 989, in
> __getitem__
> raise KeyError(key)
> KeyError: 'AssertionMessage'
>
> I've spent some time digging into this and it seems "print
> __glib_assert_msg" is behaving differently and has been for a bit.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1651623
>
> Title:
>   adt tests fail on zesty for apport
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/
> 1651623/+subscriptions
>


-- 
Regards,

Dimitri.

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

Title:
  adt tests fail on zesty for apport

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Yakkety:
  New
Status in apport source package in Zesty:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz

  fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 269651] Re: console-kit-daemon crashed with SIGSEGV in g_str_hash()

[Thomas]

can somebody report this spam, to that it can be removed?

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

Title:
  console-kit-daemon crashed with SIGSEGV in g_str_hash()

Status in ConsoleKit:
  Fix Released
Status in consolekit package in Ubuntu:
  Fix Released
Status in consolekit source package in Hardy:
  Won't Fix
Status in consolekit source package in Intrepid:
  Fix Released

Bug description:
  Binary package hint: consolekit

  i'm playing music with rhythymbox.. and the console- kit is falling
  down

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/sbin/console-kit-daemon
  NonfreeKernelModules: ath_hal
  Package: consolekit 0.2.10-1ubuntu4
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/sbin/console-kit-daemon
  ProcEnviron:
   
  Signal: 11
  SourcePackage: consolekit
  StacktraceTop:
   g_str_hash () from /usr/lib/libglib-2.0.so.0
   ?? () from /usr/lib/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: console-kit-daemon crashed with SIGSEGV in g_str_hash()
  Uname: Linux 2.6.27-2-generic i686
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/consolekit/+bug/269651/+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 1451525] Re: package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances o

[Mark Mentovai]

Reported upstream at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=861974.

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

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

Title:
  package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/curl-config',
  which is different from other instances of package libcurl4-gnutls-
  dev:i386

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  i install i386 version on amd64

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libcurl4-gnutls-dev 7.37.1-1ubuntu3.4
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: amd64
  Date: Mon May  4 18:22:25 2015
  DuplicateSignature: package:libcurl4-gnutls-dev:7.37.1-1ubuntu3.4:trying to 
overwrite shared '/usr/bin/curl-config', which is different from other 
instances of package libcurl4-gnutls-dev:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/curl-config', which is 
different from other instances of package libcurl4-gnutls-dev:i386
  SourcePackage: curl
  Title: package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is 
different from other instances of package libcurl4-gnutls-dev:i386
  UpgradeStatus: Upgraded to utopic on 2015-04-27 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1451525/+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 1059185] Re: bluetooth-wizard doesn't find any devices

[Rolf Leggewie]

@Daniel, have you even bothered to actually read this ticket?  Comment
#11, for example?

Who gives a hoot about Quantal EOL in this case?  Since you are paid you
ought to do a lot better.

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

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  bluetooth-wizard doesn't find any devices

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  I have just upgrade to Quantal from Precise.
  I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and 
mouse. They worked without problems before the upgrade, but now they don't. I 
removed them and tried to add them again, but the bluetooth-wizard is stuck 
searching for devices, and doesn't find any.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-bluetooth 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 30 11:45:37 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Christian Reis]

FWIW I continue to face this issue specifically when suspending while
using the mobile broadband connection(predictable interface name
wwp0s29u1u4i6) on my x220. I noticed this thread:

  https://mail.gnome.org/archives/networkmanager-
list/2016-September/msg0.html

Which notes this command is a workaround:

  busctl call org.freedesktop.NetworkManager /org/freedesktop/NetworkManager 
org.freedesktop.NetworkManager 
Reload "u" 4

and a link to an upstream bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1367772 -- I do wonder
whether the fix we've adopted has diverged from what's recommended
there, since it's reported to fix the OP's issue.

** Bug watch added: Red Hat Bugzilla #1367772
   https://bugzilla.redhat.com/show_bug.cgi?id=1367772

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Christian Reis]

Hmm, just noticed this is likely the same patch merged here -- well, I'm
running the latest Xenial packages:

ii  dnsmasq-base2.75-1ubuntu0.16.04.1   
  amd64Small caching DNS proxy and DHCP/TFTP server
ii  network-manager 1.2.6-0ubuntu0.16.04.1  
  amd64network management framework (daemon and 
userspace tools)

And I am still seeing the same behaviour.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Christian Reis]

Hmm, just noticed this is likely the same patch merged here -- well, I'm
running the latest Xenial packages:

ii  dnsmasq-base2.75-1ubuntu0.16.04.1   
  amd64Small caching DNS proxy and DHCP/TFTP server
ii  network-manager 1.2.6-0ubuntu0.16.04.1  
  amd64network management framework (daemon and 
userspace tools)

And I am still seeing the same behaviour.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1688920] [NEW] INFO: task systemd-udevd:326 blocked for more than 120 seconds.

[Cristian Aravena Romero]

Public bug reported:

dmesg:
[  605.178422] INFO: task systemd-udevd:326 blocked for more than 120 seconds.
[  605.178434]   Not tainted 4.11.0-041100rc8-generic #201704232131
[  605.178437] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  605.178442] systemd-udevd   D0   326  1 0x0104
[  605.178449] Call Trace:
[  605.178467]  __schedule+0x3c6/0x8c0
[  605.178474]  schedule+0x36/0x80
[  605.178479]  schedule_preempt_disabled+0xe/0x10
[  605.178484]  __mutex_lock.isra.5+0x26d/0x4e0
[  605.178492]  __mutex_lock_slowpath+0x13/0x20
[  605.178497]  ? __mutex_lock_slowpath+0x13/0x20
[  605.178501]  mutex_lock+0x2f/0x40
[  605.178508]  __blkdev_get+0x121/0x440
[  605.178513]  blkdev_get+0x12a/0x330
[  605.178519]  blkdev_open+0x5b/0x70
[  605.178523]  do_dentry_open+0x20a/0x310
[  605.178528]  ? bd_acquire+0xd0/0xd0
[  605.178533]  vfs_open+0x4e/0x80
[  605.178540]  path_openat+0x623/0x1500
[  605.178546]  ? kernfs_seq_stop_active+0x2b/0x30
[  605.178552]  do_filp_open+0x99/0x110
[  605.178558]  ? _crng_backtrack_protect+0x62/0x80
[  605.178562]  ? __check_object_size+0x100/0x19d
[  605.178567]  do_sys_open+0x130/0x220
[  605.178571]  ? do_sys_open+0x130/0x220
[  605.178576]  SyS_open+0x1e/0x20
[  605.178582]  do_syscall_64+0x5b/0xc0
[  605.178586]  entry_SYSCALL64_slow_path+0x25/0x25
[  605.178590] RIP: 0033:0x7f4a8b59bd70
[  605.178593] RSP: 002b:7fff0a24e0b8 EFLAGS: 0246 ORIG_RAX: 
0002
[  605.178598] RAX: ffda RBX: 7fff0a24e150 RCX: 7f4a8b59bd70
[  605.178600] RDX: 561d1157fd23 RSI: 000a0800 RDI: 561d12af1c10
[  605.178603] RBP: 7fff0a24e600 R08: 561d1157f400 R09: 
[  605.178605] R10: 561d12ab4e40 R11: 0246 R12: 7fff0a24e260
[  605.178607] R13: 561d12aa2010 R14: 561d12aaa0e0 R15: 7fff0a24e130

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-21ubuntu3
Uname: Linux 4.11.0-041100-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat May  6 17:13:05 2017
InstallationDate: Installed on 2015-07-26 (650 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-041100-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug zesty

** Attachment added: "dmesg_4.11.0-041100rc8-generic.txt"
   
https://bugs.launchpad.net/bugs/1688920/+attachment/4872754/+files/dmesg_4.11.0-041100rc8-generic.txt

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

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

Title:
  INFO: task systemd-udevd:326 blocked for more than 120 seconds.

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

Bug description:
  dmesg:
  [  605.178422] INFO: task systemd-udevd:326 blocked for more than 120 seconds.
  [  605.178434]   Not tainted 4.11.0-041100rc8-generic #201704232131
  [  605.178437] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  605.178442] systemd-udevd   D0   326  1 0x0104
  [  605.178449] Call Trace:
  [  605.178467]  __schedule+0x3c6/0x8c0
  [  605.178474]  schedule+0x36/0x80
  [  605.178479]  schedule_preempt_disabled+0xe/0x10
  [  605.178484]  __mutex_lock.isra.5+0x26d/0x4e0
  [  605.178492]  __mutex_lock_slowpath+0x13/0x20
  [  605.178497]  ? __mutex_lock_slowpath+0x13/0x20
  [  605.178501]  mutex_lock+0x2f/0x40
  [  605.178508]  __blkdev_get+0x121/0x440
  [  605.178513]  blkdev_get+0x12a/0x330
  [  605.178519]  blkdev_open+0x5b/0x70
  [  605.178523]  do_dentry_open+

[Touch-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Jeremy Bicha]

** Tags removed: gnome-1710
** Tags added: gnome-17.10

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

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

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

[Jeremy Bicha]

** Tags removed: gnome-1710
** Tags added: gnome-17.10 xenial yakkety

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

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

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in gnome-online-accounts source package in Xenial:
  Triaged
Status in gnome-online-accounts source package in Yakkety:
  Triaged
Status in gnome-online-accounts source package in Zesty:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+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 1688920] Re: INFO: task systemd-udevd:326 blocked for more than 120 seconds.

[Bug Watch Updater]

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

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

Title:
  INFO: task systemd-udevd:326 blocked for more than 120 seconds.

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

Bug description:
  dmesg:
  [  605.178422] INFO: task systemd-udevd:326 blocked for more than 120 seconds.
  [  605.178434]   Not tainted 4.11.0-041100rc8-generic #201704232131
  [  605.178437] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  605.178442] systemd-udevd   D0   326  1 0x0104
  [  605.178449] Call Trace:
  [  605.178467]  __schedule+0x3c6/0x8c0
  [  605.178474]  schedule+0x36/0x80
  [  605.178479]  schedule_preempt_disabled+0xe/0x10
  [  605.178484]  __mutex_lock.isra.5+0x26d/0x4e0
  [  605.178492]  __mutex_lock_slowpath+0x13/0x20
  [  605.178497]  ? __mutex_lock_slowpath+0x13/0x20
  [  605.178501]  mutex_lock+0x2f/0x40
  [  605.178508]  __blkdev_get+0x121/0x440
  [  605.178513]  blkdev_get+0x12a/0x330
  [  605.178519]  blkdev_open+0x5b/0x70
  [  605.178523]  do_dentry_open+0x20a/0x310
  [  605.178528]  ? bd_acquire+0xd0/0xd0
  [  605.178533]  vfs_open+0x4e/0x80
  [  605.178540]  path_openat+0x623/0x1500
  [  605.178546]  ? kernfs_seq_stop_active+0x2b/0x30
  [  605.178552]  do_filp_open+0x99/0x110
  [  605.178558]  ? _crng_backtrack_protect+0x62/0x80
  [  605.178562]  ? __check_object_size+0x100/0x19d
  [  605.178567]  do_sys_open+0x130/0x220
  [  605.178571]  ? do_sys_open+0x130/0x220
  [  605.178576]  SyS_open+0x1e/0x20
  [  605.178582]  do_syscall_64+0x5b/0xc0
  [  605.178586]  entry_SYSCALL64_slow_path+0x25/0x25
  [  605.178590] RIP: 0033:0x7f4a8b59bd70
  [  605.178593] RSP: 002b:7fff0a24e0b8 EFLAGS: 0246 ORIG_RAX: 
0002
  [  605.178598] RAX: ffda RBX: 7fff0a24e150 RCX: 
7f4a8b59bd70
  [  605.178600] RDX: 561d1157fd23 RSI: 000a0800 RDI: 
561d12af1c10
  [  605.178603] RBP: 7fff0a24e600 R08: 561d1157f400 R09: 

  [  605.178605] R10: 561d12ab4e40 R11: 0246 R12: 
7fff0a24e260
  [  605.178607] R13: 561d12aa2010 R14: 561d12aaa0e0 R15: 
7fff0a24e130

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu3
  Uname: Linux 4.11.0-041100-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May  6 17:13:05 2017
  InstallationDate: Installed on 2015-07-26 (650 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-041100-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1688920/+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 189617] Re: policykit integration missing

[Jeremy Bicha]

** Tags added: gnome-17.10 wayland

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

Title:
  policykit integration missing

Status in gdebi package in Ubuntu:
  Triaged
Status in gdebi package in Debian:
  New

Bug description:
  Binary package hint: gdebi

  this package is missing policykit bindings
  version 0.3.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/189617/+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 1688933] [NEW] systemd restart-loops logind

[Thomas Mayer]

Public bug reported:

Syslog logs systemd trying to restart logind every few seconds:

May  7 00:51:29 server systemd[1]: Starting Login Service...
May  7 00:51:54 server systemd[1]: systemd-logind.service: Main process exited, 
code=exited, status=1/FAILURE
May  7 00:51:54 server systemd[1]: Failed to start Login Service.
May  7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered failed 
state.
May  7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
May  7 00:51:54 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
May  7 00:51:54 server systemd[1]: Stopped Login Service.
May  7 00:51:54 server systemd[1]: Starting Login Service...
May  7 00:52:19 server systemd[1]: systemd-logind.service: Main process exited, 
code=exited, status=1/FAILURE
May  7 00:52:19 server systemd[1]: Failed to start Login Service.
May  7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered failed 
state.
May  7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
May  7 00:52:19 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
May  7 00:52:19 server systemd[1]: Stopped Login Service.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun May  7 00:51:07 2017
InstallationDate: Installed on 2013-08-21 (1353 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic 
root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 
 2 overridden configuration files found.
UpgradeStatus: Upgraded to xenial on 2016-10-24 (193 days ago)
dmi.bios.date: 03/13/2014
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SWQ6710H.86A.0067.2014.0313.1347
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DQ67OW
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG12528-309
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0067.2014.0313.1347:bd03/13/2014:svn:pn:pvr:rvnIntelCorporation:rnDQ67OW:rvrAAG12528-309:cvn:ct3:cvr:

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

Title:
  systemd restart-loops logind

Status in systemd package in Ubuntu:
  New

Bug description:
  Syslog logs systemd trying to restart logind every few seconds:

  May  7 00:51:29 server systemd[1]: Starting Login Service...
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
  May  7 00:51:54 server systemd[1]: Failed to start Login Service.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered 
failed state.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
  May  7 00:51:54 server systemd[1]: Stopped Login Service.
  May  7 00:51:54 server systemd[1]: Starting Login Service...
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
  May  7 00:52:19 server systemd[1]: Failed to start Login Service.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered 
failed state.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
  May  7 00:52:19 server systemd[1]: Stopped Login Service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun May  7 00:51:07 2017
  InstallationDate: Installed on 2013-08-21 (1353 days ago)
  InstallationMedia: Ubunt

[Touch-packages] [Bug 1684973] Re: Crashes (segfault) under Wayland in Ubuntu GNOME 17.04

[Jeremy Bicha]

** Tags added: gnome-17.10 wayland

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

Title:
  Crashes (segfault) under Wayland in Ubuntu GNOME 17.04

Status in gdebi package in Ubuntu:
  New

Bug description:
  While trying to run gdebi-gtk to install a .deb package, program won't
  open under Wayland session. Running from terminal produces the
  following:

  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  Segmentation fault (core dumped)

  BUG DISCOVERED RUNNING
  Ubuntu GNOME 17.04 x64
  GNOME 3.24.0 desktop environment
  Wayland session
  Linux kernel 4.10.0-19-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1684973/+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 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

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

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1688721/+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 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected

[Christopher M. Penalver]

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

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

Title:
  Mouse flickers and disappears on primary monitor when additional
  monitor is connected

Status in xorg package in Ubuntu:
  New

Bug description:
  Any time I connect my Acer G236HL LCD monitor with VGA via my
  Displaylink adapter (DisplayLink driver version 1.2.65), the mouse
  flickers and disappears in the primary monitor. It displays perfectly
  on the additional monitor. It also displays perfectly after the
  additional monitor is disconnected.

  I see that there are a number of similar bug reports:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan 10 22:34:58 2017
  DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could 
not locate dkms.conf file.
   File:  does not exist.

   bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2016-01-26 (350 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash 
usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago)
  XorgLogOld:

  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Jan 10 20:18:19 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.4-1ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1655828/+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 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected

[Christopher M. Penalver]

Mauricio Maluff Masi, given this issue is correlated to using the
DisplayLink driver/adapter, in order to report this issue to them, could
you please test the latest driver version (1.3.52) via
http://www.displaylink.com/downloads/ubuntu and advise to the results?

** Description changed:

- Any time I connect my Acer G236HL LCD monitor with VGA via my
- Displaylink adapter (DisplayLink driver version 1.2.65), the mouse
+ Any time I connect my Acer G236HL LCD monitor with VGA via my Dell
+ Adapter (Part# 470-ABHH, DisplayLink driver version 1.2.65), the mouse
  flickers and disappears in the primary monitor. It displays perfectly on
  the additional monitor. It also displays perfectly after the additional
  monitor is disconnected.
  
  I see that there are a number of similar bug reports:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001
+ 
+ WORKAROUND: Bypass the DisplayLink adapter and plug computer directly
+ into a monitor with mini-DP.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan 10 22:34:58 2017
  DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could 
not locate dkms.conf file.
   File:  does not exist.
  
   bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2016-01-26 (350 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash 
usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago)
  XorgLogOld:
  
  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Jan 10 20:18:19 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.4-1ubuntu6.1

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

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

Title:
  Mouse flickers and disappears on primary monitor when additional
  monitor is connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Any time I connect my Acer G236HL LCD monitor with VGA via my

[Touch-packages] [Bug 1682030] Re: package resolvconf 1.78ubuntu2 failed to install/upgrade: package resolvconf is not ready for configuration cannot configure (current status 'half-installed')

[Launchpad Bug Tracker]

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

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

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

Title:
  package resolvconf 1.78ubuntu2 failed to install/upgrade: package
  resolvconf is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  I have no idea what is happening

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   resolvconf: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr 12 00:39:21 2017
  DpkgTerminalLog:
   dpkg: error processing package resolvconf (--configure):
package resolvconf is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package resolvconf is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-04-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: package 
resolvconf 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/resolvconf/+bug/1682030/+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 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected

[Mauricio Maluff Masi]

Actually I got tired of this and got a new monitor that supports the DP
port on my laptop. I no longer have the old one, so I can't test this any
further. I suppose that means it can be closed?

On Sat, May 6, 2017, 21:15 Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Mauricio Maluff Masi, given this issue is correlated to using the
> DisplayLink driver/adapter, in order to report this issue to them, could
> you please test the latest driver version (1.3.52) via
> http://www.displaylink.com/downloads/ubuntu and advise to the results?
>
> ** Description changed:
>
> - Any time I connect my Acer G236HL LCD monitor with VGA via my
> - Displaylink adapter (DisplayLink driver version 1.2.65), the mouse
> + Any time I connect my Acer G236HL LCD monitor with VGA via my Dell
> + Adapter (Part# 470-ABHH, DisplayLink driver version 1.2.65), the mouse
>   flickers and disappears in the primary monitor. It displays perfectly on
>   the additional monitor. It also displays perfectly after the additional
>   monitor is disconnected.
>
>   I see that there are a number of similar bug reports:
>   https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891
>   https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300
>   https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223
>   https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001
> +
> + WORKAROUND: Bypass the DisplayLink adapter and plug computer directly
> + into a monitor with mini-DP.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: xorg 1:7.7+13ubuntu4
>   ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
>   Uname: Linux 4.8.0-34-generic x86_64
>   NonfreeKernelModules: wl
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.3-0ubuntu8.2
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Tue Jan 10 22:34:58 2017
>   DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from
> PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to
> execute child process "./xorg_fix_proprietary.py" (No such file or
> directory) (8))
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-trusty-amd64-20140620-0
>   DistroCodename: yakkety
>   DistroVariant: ubuntu
>   DkmsStatus:
>bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError!
> Could not locate dkms.conf file.
>File:  does not exist.
>
>bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00
> [VGA controller])
>  Subsystem: Dell HD Graphics 5500 [1028:0665]
>   InstallationDate: Installed on 2016-01-26 (350 days ago)
>   InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary
> 20140620-04:25
>   MachineType: Dell Inc. XPS 13 9343
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic
> root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash
> usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago)
>   XorgLogOld:
>
>   dmi.bios.date: 08/29/2016
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A09
>   dmi.board.name: 0TM99H
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: XPS 13 9343
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.70-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.2-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160706-1ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
>   xserver.bootTime: Tue Jan 10 20:18:19 2017
>   xserver.configfile: default
>   xserver.errors: modeset(G0): glamor initialization failed
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id5152
>vendor SHP
>   xserver.version: 2:1.18.4-1ub

[Touch-packages] [Bug 1668802] Re: /lib/systemd/systemd-journald:6:journal_file_entry_array_n_items:link_entry_into_array:journal_file_link_entry:journal_file_append_entry_internal:journal_file_append

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  /lib/systemd/systemd-
  
journald:6:journal_file_entry_array_n_items:link_entry_into_array:journal_file_link_entry:journal_file_append_entry_internal:journal_file_append_entry

Status in systemd package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
231-9ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5d26a3a04bae890ad487f4cdead3465032fa8828 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668802/+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 1686544] Re: sudo fails to retrieve groups in sudoUser

[quess]

sudoUser=%#gid is a known bug in sssd
https://pagure.io/SSSD/sssd/issue/1678

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

Title:
  sudo fails to retrieve groups in sudoUser

Status in sudo package in Ubuntu:
  New

Bug description:
  Currently using sudo with sssd 1.13.4 on xenial to manage sudo rules,
  groups are not resolved since last update.

  I troubleshooted :
  - sudo with all@debug
  - sssd with [sudo] debug_level = 9 and [domain/domain.tld] debug_level = 9
  - LDAP requests are correctly sent, and I can obtain correct rules
  - SSSD cache is correctly stored too, I can successfully ldbsearch into!

  I had to downgrade sudo (1.8.16-0ubuntu1.3) xenial to sudo
  (1.8.16-0ubuntu1) xenial, to get my groups working again. I tried sudo
  1.8.19, with no luck.

  
  Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: ALL

  Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: #uid

  Broken since 1.8.16-0ubuntu1.3:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: %mygroup

  Broken in 1.8.16-0ubuntu1.3:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: myuser

  
  Patch sssd-doesnt-handle-netgroups.diff seems to break something...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1686544/+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