[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Florian W.]

Using artful, I updated these packages (everything that used to have version 
"17.2.2-0ubuntu1" on my system) to version "17.2.4-0ubuntu1~17.10.1" from 
-proposed:
libegl1-mesa:amd64 libgbm1:amd64 libgl1-mesa-dev:amd64 libgl1-mesa-dri:amd64 
libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-glx:i386 
libglapi-mesa:amd64 libglapi-mesa:i386 libgles2-mesa:amd64 
libwayland-egl1-mesa:amd64 libxatracker2:amd64 mesa-common-dev:amd64 
mesa-vdpau-drivers:amd64 mesa-vulkan-drivers:amd64

After a reboot, I can confirm Lawrence's observation that vulkan-
smoketest segfaulted on the old version, but seems to work fine using
the version from -proposed.

Since Lawrence forgot to remove the verification-needed-artful tag, I'm
going to remove it now.

** Tags removed: verification-needed-artful

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1322178] Re: new armhf click build chroot is DEB_BUILD_ARCH=amd64

[Florian W.]

This is still an issue, and very confusing. I assume that most
developers who need external dependenices for the click package run into
this and wonder why the linker complains about not finding the library.

I guess most developers find it more convenient to add build rules that
copy prebuilt libraries from the chroot into the click package instead
of adding the library source code to their project. This ensures easy
click package updates whenever Ubuntu updates the library (without API
breaking changes of course). For this use case, running apt-get install
libwhatever-dev in the chroot is the first required step, and the user
expects to have a somewhat sane environment when clicking the "Maintain"
button.

I worked around this by installing libupnp6:armhf and libupnp6-dev:armhf
instead of libupnp-dev.

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

Title:
  new armhf click build chroot is DEB_BUILD_ARCH=amd64

Status in The Savilerow project:
  New
Status in click package in Ubuntu:
  Confirmed

Bug description:
  (note sure which project to file this against..)

  I just created a 14.04 armhf click build target from the Ubuntu SDK.

  A terminal into the chroot (from the Maintain button) shows this:

  (click-ubuntu-sdk-14.04-armhf)root@chroma:/home/knitzsche# dpkg-architecture 
  DEB_BUILD_ARCH=amd64
  DEB_BUILD_ARCH_BITS=64
  DEB_BUILD_ARCH_CPU=amd64
  DEB_BUILD_ARCH_ENDIAN=little
  DEB_BUILD_ARCH_OS=linux
  DEB_BUILD_GNU_CPU=x86_64
  DEB_BUILD_GNU_SYSTEM=linux-gnu
  DEB_BUILD_GNU_TYPE=x86_64-linux-gnu
  DEB_BUILD_MULTIARCH=x86_64-linux-gnu
  DEB_HOST_ARCH=amd64
  DEB_HOST_ARCH_BITS=64
  DEB_HOST_ARCH_CPU=amd64
  DEB_HOST_ARCH_ENDIAN=little
  DEB_HOST_ARCH_OS=linux
  DEB_HOST_GNU_CPU=x86_64
  DEB_HOST_GNU_SYSTEM=linux-gnu
  DEB_HOST_GNU_TYPE=x86_64-linux-gnu
  DEB_HOST_MULTIARCH=x86_64-linux-gnu

  I expected (perhaps naively) :DEB_BUILD_ARCH=armhf (and probably
  others).

  When I install pkgs in the chroot with apt-get install, the amd64 arch
  one is installed unless I specify armhf, which I did not expect
  either.

  Some pkgs/vers on my host system:
  $ apt-cache policy qtcreator-plugin-ubuntu
  qtcreator-plugin-ubuntu:
Installed: 3.0.1+14.10.20140521.1-0ubuntu1~0trusty1

  $ apt-cache policy click
  click:
Installed: 0.4.23.1ubuntu1i~0trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1322178/+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 1241185] Re: Should provide policy based lifecycle exceptions

[Florian W.]

Since you want to mark this bug as "Won't fix", can you point me to some
docs for music-hub? I can only find some info about
QtMultimedia.MediaPlayer related to music-hub, but that QML API is
apparently missing the functionality described in this bug report.

I'm already using QtMultimedia.MediaPlayer, and while that allows me to
keep playing the current song when the display turns off or I switch to
another app, which is already a huge improvement over the state from
~1.5 years ago when I tried this the last time, it's still not even
close to "good enough".

When the current song ends, the MediaPlayer.onStatusChanged signal is
not executed immediately, but only after I switch back to my app or
unlock the phone. As far as I can tell, that signal is the only place
where I could start playback of the next song. So it's just silent after
the current song ends, clearly a very bad user experience.

You should either allow apps to run the slot connected to that signal
whenever it is fired (which might be pretty difficult to solve and opens
up a lifecycle policy exploit), or add a queue API to QtMultimedia /
some other QML namespace. (On a related note, a signal like
"playbackAboutToFinish" could allow implementing gapless playback in the
future.)

If you do the queue thing, make sure to support programatically deleting
from the queue before the media is played: I want to implement "play
next song from my app's queue, or if the user has not enqueued any
songs, play next song from album". If I am supposed to use the music-app
queue, I have to enqueue all the remaining songs on the current album
when playback starts. If a user then adds something to the app queue, I
must be able to remove everything from the music-hub queue, add the
user-provided song, then add every song following the newly enqueued
song on its album.

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

Title:
  Should provide policy based lifecycle exceptions

Status in Qt integration with the Mir display server:
  New
Status in Unity Mir:
  Triaged
Status in unity-mir package in Ubuntu:
  Triaged

Bug description:
  Currently, unity-mir has a hard coded exception to prevent music-app
  from suspending when losing focus.  We need a way to allow other apps
  to continue playback of music, etc.  For example, I've tried to help
  get panpipe (pandora app) usable on the phone, however without the
  ability to playback continuously it isn't useful.

  Perhaps lifecycle management exceptions based on apparmor-easyprof-
  ubuntu policy?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1241185/+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 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2

[Florian W.]

Is there any way to preserve wine, libsdl-*-dev and qt5 when installing
the hardware enablement bits on 14.04 (with -proposed disabled)?

I tried the suggested apt command lines, but none of them seemed to
install the new mesa/xorg stack and preserve wine/qt5/libsdl at the same
time. See the attached apt output.

** Attachment added: "apt-hwe.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1400626/+attachment/4315207/+files/apt-hwe.txt

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

Title:
  Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
  14.04.2

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-snapshot package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-fonts package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xtrans package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Released
Status in llvm-toolchain-snapshot source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Fix Released
Status in x11proto-fonts source package in Trusty:
  Fix Released
Status in xorg source package in Trusty:
  Fix Committed
Status in xtrans source package in Trusty:
  Fix Released

Bug description:
  In order to upload the new xorg-server we need to backport the following 
packages from utopic:
  libdrm
  x11proto-core
  x11proto-fonts
  xtrans

  libdrm 2.4.52-1->2.4.56-1 seems to have the following changes:
  - Hides private symbols from all libdrm libraries
  - fixes MSAA on Hawaii (radeon).
  - Adds cherryview pci-ids (intel).
  - Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
  - Fixes to exynos and freedreno.
  - Enables building libdrm-freedreno1 and libdrm-exynos1

  x11proto-core's main change appears to be changing from the 'pointer' type to 
'void *':
  
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz

  x11proto-fonts' main change is the same as x11proto-core, but the 
documentation is reformatted too:
  
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz

  xtrans seems to have 2 minor changes, increase default unix pipe size and add 
support for systemd socket activation:
  https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz

  xorg needs to be slightly updated, to allow xserver-xorg to provide
  the unrenamed lts-utopic, and to allow xorg to be installed with the
  renamed xorg-server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+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 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2

[Florian W.]

Thanks, Maarten. I just noticed my comment was missing the apt command
that I used.

I now use

> LANG=C sudo apt install --install-recommends libgles2-mesa-lts-utopic
libglapi-mesa-lts-utopic linux-generic-lts-utopic xserver-xorg-lts-
utopic libgl1-mesa-dri-lts-utopic libegl1-mesa-drivers-lts-utopic libgl1
-mesa-glx-lts-utopic:i386

and now wine is preserved. However, I still lose qt5-default,
qtbase5-dev and some other qt5 libs, and also libsdl2-2.0-0 and related
sdl libs, and some random other libs where I'm not sure I really need
them (I guess not). Adding qt5-default and qtbase5-dev to the command
leads to http://paste.ubuntu.com/10141032/ (I already have the utopic
kernel, so that note there by apt is correct).

I'm not sure if this is a bug in one of the backported packages, or
another package, or even my system setup or apt skills. Since #16 and
#13 apparently had the same issue, it might be related. Let me know if
this is not the right place to post this. :-)

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

Title:
  Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
  14.04.2

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-snapshot package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-fonts package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xtrans package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Released
Status in llvm-toolchain-snapshot source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Fix Released
Status in x11proto-fonts source package in Trusty:
  Fix Released
Status in xorg source package in Trusty:
  Fix Committed
Status in xtrans source package in Trusty:
  Fix Released

Bug description:
  In order to upload the new xorg-server we need to backport the following 
packages from utopic:
  libdrm
  x11proto-core
  x11proto-fonts
  xtrans

  libdrm 2.4.52-1->2.4.56-1 seems to have the following changes:
  - Hides private symbols from all libdrm libraries
  - fixes MSAA on Hawaii (radeon).
  - Adds cherryview pci-ids (intel).
  - Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
  - Fixes to exynos and freedreno.
  - Enables building libdrm-freedreno1 and libdrm-exynos1

  x11proto-core's main change appears to be changing from the 'pointer' type to 
'void *':
  
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz

  x11proto-fonts' main change is the same as x11proto-core, but the 
documentation is reformatted too:
  
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz

  xtrans seems to have 2 minor changes, increase default unix pipe size and add 
support for systemd socket activation:
  https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz

  xorg needs to be slightly updated, to allow xserver-xorg to provide
  the unrenamed lts-utopic, and to allow xorg to be installed with the
  renamed xorg-server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+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 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2

[Florian W.]

I tried this again now, and after installing libgl1-mesa-dev-lts-utopic
I was able to re-install qt5-default and qtbase5-dev, and then ubuntu-
sdk.

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

Title:
  Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
  14.04.2

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-snapshot package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-fonts package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid
Status in xtrans package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Released
Status in llvm-toolchain-snapshot source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Fix Released
Status in x11proto-fonts source package in Trusty:
  Fix Released
Status in xorg source package in Trusty:
  Fix Committed
Status in xtrans source package in Trusty:
  Fix Released

Bug description:
  In order to upload the new xorg-server we need to backport the following 
packages from utopic:
  libdrm
  x11proto-core
  x11proto-fonts
  xtrans

  libdrm 2.4.52-1->2.4.56-1 seems to have the following changes:
  - Hides private symbols from all libdrm libraries
  - fixes MSAA on Hawaii (radeon).
  - Adds cherryview pci-ids (intel).
  - Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
  - Fixes to exynos and freedreno.
  - Enables building libdrm-freedreno1 and libdrm-exynos1

  x11proto-core's main change appears to be changing from the 'pointer' type to 
'void *':
  
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz

  x11proto-fonts' main change is the same as x11proto-core, but the 
documentation is reformatted too:
  
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz

  xtrans seems to have 2 minor changes, increase default unix pipe size and add 
support for systemd socket activation:
  https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz

  xorg needs to be slightly updated, to allow xserver-xorg to provide
  the unrenamed lts-utopic, and to allow xorg to be installed with the
  renamed xorg-server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+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 1422989] [NEW] emulator: mtp-server fails to start, respawns immediately -> high CPU load / log spam

[Florian W.]

Public bug reported:

I think the bug title and the logs attached by ubuntu-bug explain my
issue:

mtp-server fails to start on emulator image 105 (devel-proposed i386)
because there is no /dev/mtp_usb device. After the process quits, it is
instantly respawned, just to fail again. The emulator is now 0% idle
because it uses all the processing ressources to spawn apport, mtp-
server and (juding by PID delta between mtp-server processes) 8 other
processes over and over again.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: mtp-server 0.0.4+15.04.20150126-0ubuntu1
Uname: Linux 3.4.0-4-goldfish i686
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
Date: Tue Feb 17 22:59:27 2015
SourcePackage: mtp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 vivid

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

Title:
  emulator: mtp-server fails to start, respawns immediately -> high CPU
  load / log spam

Status in mtp package in Ubuntu:
  New

Bug description:
  I think the bug title and the logs attached by ubuntu-bug explain my
  issue:

  mtp-server fails to start on emulator image 105 (devel-proposed i386)
  because there is no /dev/mtp_usb device. After the process quits, it
  is instantly respawned, just to fail again. The emulator is now 0%
  idle because it uses all the processing ressources to spawn apport,
  mtp-server and (juding by PID delta between mtp-server processes) 8
  other processes over and over again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mtp-server 0.0.4+15.04.20150126-0ubuntu1
  Uname: Linux 3.4.0-4-goldfish i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Tue Feb 17 22:59:27 2015
  SourcePackage: mtp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1422989/+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 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG

[Florian W.]

Concerning the "bootspeed" tag, the NM issue would be less noticable if
"rc-local.service" was removed from "After=" in plymouth-quit.service.
That way, my boot-to-graphical-login is a few seconds faster because
plymouth is only visible for a very very short time instead of waiting
up to 8 seconds for the network to come up. I did that using systemd
override, and now my boot on kernel 4.4 is almost as fast as it was in
16.04.

Of course, technically the full boot including nmbd etc. still takes the
same time because NM is still slow, but I don't really care if nmbd is
up when I type my password into lightdm. The only thing that matters to
me is that I can type my password and then fire up Chromium, by which
time the network generally is ready to use in my case.

But maybe there's a good reason for some people to have rc.local
executed (and therefor network ready to use) before starting lightdm.

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

Title:
  NetworkManager takes very long to start, or times out, blocked on RNG

Status in Auto Package Testing:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in network-manager package in Debian:
  New

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Sep 13 10:05:05 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   source-directory interfaces.d
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1622893/+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 1360026] Re: Libav11 for Utopic

[Florian W.]

So in Debian, all the packages in testing are now built against libav11 AFAICT.
I (as a user) hope we can still get libav11 for Utopic.

In case this helps with your decision, these are the packages in sid
which are not built against libav11 (yet?):

- bino (unrelated to libav, some gettext related version mismatch)
- gnash (probably unrelated, FTBFS on armel because armel has std::future 
issues, and FTBFS on mips for whatever reason)
- gstreamer0.10-ffmpeg (FTBFS since libav9)
- jitsi (unrelated, complains about invalid -d command line option for apt … ?!)
- mrpt (there was no attempt to build against libav11 for any main arch yet, 
since there seem to be unrelated build issues on some arches. Building on alpha 
architecture at ports.debian.org against libav11 succeeded recently.)
- taoframework (language bindings that need updating for libav9+. Upstream 
probably cared about ffmpeg only and is dead now anyway.)
- visp (probably unrelated, test suite failure on powerpc)
- zoneminder (FTBFS since libav10 at least, still using CODEC_ID_*)

I'm not sure if Ubuntu carries any additional packages that would fail
to build against libav11. Also not sure about the current Ubuntu state
of the packages I mentioned. Maybe some of them need to be dropped from
the archive.

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

Title:
  Libav11 for Utopic

Status in “libav” package in Ubuntu:
  Confirmed
Status in “libav” package in Debian:
  Fix Committed

Bug description:
  This ticket is to track the Libav11 transition in Utopic.

  See the discussion on the Mailing list on
  https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038435.html

  The transition is being staged in
  https://launchpad.net/~motumedia/+archive/ubuntu/libav11/+packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1360026/+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 1360026] Re: Libav11 for Utopic

[Florian W.]

To clarify:
- So in Debian, all the packages in testing are now built against libav11 
AFAICT.

I actually meant:
The packages that are both in sid and in testing were successfully rebuilt 
against libav11. However, they are still in sid and waiting to migrate. :-)

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

Title:
  Libav11 for Utopic

Status in “libav” package in Ubuntu:
  Confirmed
Status in “libav” package in Debian:
  Fix Committed

Bug description:
  This ticket is to track the Libav11 transition in Utopic.

  See the discussion on the Mailing list on
  https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038435.html

  The transition is being staged in
  https://launchpad.net/~motumedia/+archive/ubuntu/libav11/+packages.

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