To be clear, that carrier is set to "failed" when retriggering uevents
is not the main problem. The main problem is that after 5-10 minutes,
networkd silently takes control again of the ethernet interface. The
retriggering of uevents and the reaction on the networkd side is just an
indication that
/etc/pam.d/login references the module:
sessionoptional pam_lastlog.so
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2060676
Title:
login: remove pam_lastlog.so
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1068229:
Package: libpam-modules
Version: 1.5.3-6
Severity: normal
I noticed the following line in my logs:
login[2449]: PAM unable to dlopen(pam_lastlog.so):
/usr/lib/security/pam_lastlog.so: cannot open shared object file:
I am seeing this on focal, when running command:
$ add-apt-repository ppa:snappy-dev/image -y
on 20.04. 22.04 seems to be fine.
The errors I see are of the same two types as those in the bug
description:
<<
Cannot add PPA: 'ppa:~snappy-dev/ubuntu/image'.
The team named '~snappy-dev' has no PPA
Related debian bug: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1031622
** Bug watch added: Debian Bug tracker #1031622
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
After installation of the FDE image, the system fails to boot due to
e2fsck failing with:
- Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
- feature(s): FEATURE_C12
+ Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
Please report this for the network-manager debian package, the snappy-
hwe-snaps is only for the network-manager snap package.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snappy-hwe-snaps
Status: New => Invalid
--
You received
Public bug reported:
There is a mismatch between what netplan expresses when using globbing
in a netplan file and what NM understands when using a match setting.
For instance:
network:
version: 2
ethernets:
all-en:
match:
name: "en*"
dhcp4:
@slyon thanks, I have manually tested and seems to work. I've created
https://github.com/snapcore/network-manager-snap/pull/15, let's see how
tests go.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
To reproduce the problem, this should be enough:
1. Create a connection to an OpenVPN server
2. Start the connection. The OpenVPN plugin will create a tunnel interface.
3. "nmcli c" should show a tunX connection and the VPN connection. "nmcli d"
should show tunX as a external connection.
4.
> So IIUC the connection works as expected, but only after reloading the
connection profiles; it doesn't show up at the time it is expected,
right?
Hm, not sure if we mean the same. That two connections (tun2 and
) appear after connecting to the VPN is expected. NM
recognizes tun2 as "external"
Changing the check as suggested to:
if (!is_volatile && !is_nm_generated && !is_external) {
...
does help and netplan files for tun0 and tun1 are not written anymore.
But, when I create a VPN connection I still have problems.
$ network-manager.nmcli c import type openvpn file
$
Unfortunately this is still happening with the patch from comment #3. In
fact I do not even need to create a VPN connection for this. If I
install easy-openvpn-server:
$ snap install easy-openvpn-server
it creates two tun devices (tun0 and tun1) that can be seen with "ip
address" command. That
It turns out that this actually regressed some qualcomm modems because
modem-manager started to use some special netlink sockets that were not
enabled in the 5.4 kernel.
To have that we need (see LP: #1998194):
CONFIG_QRTR=m
CONFIG_QRTR_SMD=m
CONFIG_QRTR_TUN=m
CONFIG_QRTR_MHI=m
in the 5.4
Right, it is more about the plugin, was not fully sure where to put
this, but now probably we can put under network-manager deb.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I have tested core20 built using the proposed pocket and I can confirm
that the issue does not appear (no failed services on start up).
I have also tested the focal deb on classic and the modprobe services do
not fail either:
root@focal:~# apt policy systemd
systemd:
Installed:
I have tested core22 built using the proposed pocket and I can confirm
that the issue is gone (no failed services on start up anymore).
I have also tested the jammy deb on classic and the modprobe services do
not fail either:
root@jammy:~# apt policy systemd
systemd:
Installed:
I have tested a modified systemd-pstore.service in UC20 (focal based)
adding:
[Unit]
After=modprobe@efi_pstore.service modprobe@mtdpstore.service
modprobe@chromeos_pstore.service modprobe@ramoops.service
modprobe@pstore_zone.service modprobe@pstore_blk.service
Wants=modprobe@efi_pstore.service
** Bug watch added: github.com/snapcore/core-base/issues #72
https://github.com/snapcore/core-base/issues/72
--
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/1982462
On Mon, Jul 25, 2022 at 4:00 PM Lukas Märdian <1982...@bugs.launchpad.net>
wrote:
> Alfonso, would this also affect Focal (Ubuntu Core 20), after this patch
> is shipped to that series via SRU (as it happened on Jammy already)?
>
> https://git.launchpad.net/~ubuntu-core-
&g
** Tags added: rls-jj-incoming
--
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/1982462
Title:
Some modprobe loading services requested by the pstore service fail
Status
Public bug reported:
[Impact]
It has been detected that some modprobe services fail on UC22 after the
jammy upgrade 249.11-0ubuntu3.4:
$ systemctl --system --no-ask-password --no-pager list-units --state=failed
Failed units:
UNIT LOAD ACTIVE SUBDESCRIPTION
●
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: snappy-hwe-snaps
--
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/1973835
Public bug reported:
lz4 is not a dependency of initramfs-tools-core, although it uses lz4cat
in the unmkinitramfs script.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
With systemd debug trace enabled.
Look for
Got message type=method_call sender=n/a destination=org.freedesktop.systemd1
path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager
member=RestartUnit cookie=22 reply_cookie=0 signature=ss error-name=n/a
error-message=n/a
**
Full journal attached
** Attachment added: "journal-fail.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958676/+attachment/5556929/+files/journal-fail.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This is what I see in a jammy lxd container:
Jan 21 17:47:55 jammy systemd[1]: Starting Load AppArmor profiles managed
internally by snapd...
Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Auto import
assertions from block devices being skipped.
Jan 21 17:47:55 jammy systemd[1]:
This fixes https://github.com/snapcore/core-initrd/issues/33. Tested by
building a core20 snap from focal proposed.
Before:
[6.611137] systemd[1]: systemd 245.4-4ubuntu3.13 running in system mode.
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS
Public bug reported:
[Impact]
A systemd regression in focal made it think that target units cannot
fail, which produced warnings like:
emergency.target: Requested dependency OnFailure=reboot.target ignored
(target units cannot fail).
So the OnFailure settings are ignored for targets (see
On Wed, Sep 29, 2021 at 1:35 PM Mattia Rizzolo
<1943...@bugs.launchpad.net> wrote:
>
> As a member of the Debian LibreOffice Team, and also as an Ubuntu
> Developer, I'm likewise not convinced that starting to build and ship
> graphite2's static library is a really useful thing to do.
>
> I'm
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757
** Bug watch added: Debian Bug tracker #994757
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Debian bug report: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=994752
** Bug watch added: Debian Bug tracker #994752
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994752
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not
possible to compile statically against this library. See attached
debdiff to solve this.
** Affects: libdrm (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "debdiff.patch"
Public bug reported:
There is no libgraphite2.a file, so it is not possible to compile
statically against this library. See attached patch to solve this.
** Affects: graphite2 (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "debdiff.patch"
Public bug reported:
The development package for pango (libpango1.0-dev) does not include
static libraries so it is not possible to link these libraries
statically.
See attached patch with the fix.
** Affects: pango1.0 (Ubuntu)
Importance: Undecided
Status: New
** Patch added:
Just FTR, note that the change in NM upstream was needed so the network-
manager snap was able to correctly detect if udevd is running. We
currently build the snap from the source package + some patches
including this one. But, the long term target is to be able to create
the snap by simply
This MR for apparmor_parser:
https://gitlab.com/apparmor/apparmor/-/merge_requests/711
helps quite a bit with accelerating the expression optimization, and
actually makes it worth enabling them back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
There is here a change in behavior in lxc/lxd. Running
https://paste.ubuntu.com/p/vz7SXcX3K9/:
On hirsute lxd container:
root@hirsute:~# ./test
access errno 13
path is read only: 0
root@hirsute:~# mount | grep 'sysfs on /sys '
sysfs on /sys type sysfs (rw,relatime)
On focal lxd container:
This iso won't install.
On Tue, Nov 3, 2020 at 8:35 PM Daniel van Vugt <1902...@bugs.launchpad.net>
wrote:
> Please run these commands:
>
> ls -l /dev/dri/* > dri.txt
> glxinfo > glx.txt
>
> and attach the resulting text files here.
>
> ** Changed in: mesa (Ubuntu)
>Status: New =>
there is no ubuntu 20 for my board.
On Tue, Nov 3, 2020 at 12:25 AM Daniel van Vugt <1902...@bugs.launchpad.net>
wrote:
> ** Summary changed:
>
> - 3d rendering is very slow
> + [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
>
> --
> You received this bug notification
Public bug reported:
3d rendering is very slow, also when surfing the internet, webpages take
a while to render. Internet access is not the problem.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.19.64+ aarch64
ApportVersion: 2.20.9-0ubuntu7.18
I have updated to focal-proposed and checked that now there is no
date: invalid date ' Wed Apr 1 17:23:44 2020'
output anymore in the console and that fixrtc finishes as expected.
$ apt info initramfs-tools
Package: initramfs-tools
Version: 0.136ubuntu6.2
...
$ cat /proc/cmdline
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: snappy-hwe-snaps
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Description changed:
The fixrtc script is failing with message:
date: invalid date ' Wed Apr 1 17:23:44 2020'
when calling the date command. It looks like it does not like the
leading spaces for the input date. The date is taken from 'dumpe2fs -h'
ouptput, and some
See attached debdiff for the fix
** Patch added: "initramfs-tools_debdiff.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+attachment/5377425/+files/initramfs-tools_debdiff.patch
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
The fixrtc script is failing with message:
date: invalid date ' Wed Apr 1 17:23:44 2020'
when calling the date command. It looks like it does not like the
leading spaces for the input date. The date is taken from 'dumpe2fs -h'
ouptput, and some clean-up on it
It looks like the VPN related SRU that was previous to this one was
reverted. Could we land this into bionic?
--
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/1781597
I have tested on xenial, the problem is solved with the change.
ubuntu@xenial:~$ apt policy resolvconf
resolvconf:
Installed: 1.78ubuntu7
Candidate: 1.78ubuntu7
Version table:
*** 1.78ubuntu7 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100
Thanks Robie, good catch. Please find attached the new patch for xenial:
I have moved a bit below the call to flock to ensure the dir was created
- the lines now out of the lock do not change any files so that should
not be a problem.
** Patch added: "xenial-debdiff.patch"
Patch for xenial.
** Description changed:
+ [Impact]
+
+ The bug can lead to non-working DNS. This is a critical bug that needs
+ to be fixed in the stable release.
+
+ The patch fixes the bug by using a file lock via the flock command.
+
+ [Test case]
+
+ This script should eventually stop
@vorlon, @tsimonq2, patch for xenial attached, and description changed
for SRU. Sponsors teamm re-subscribed.
** Summary changed:
- resolvconf is racy, which leads to broken resolv.conf in parallel calls
+ [SRU] resolvconf is racy, which leads to broken resolv.conf in parallel calls
--
You
I would very much like the SRU to happen.
--
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/1781597
Title:
[SRU] WoWLAN settings are not supported
Status in
** Patch added: "debdiff.patch"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+attachment/5256569/+files/debdiff.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Public bug reported:
It has been found that simultaneous calls to resolvconf can lead to
inconsistent content in resolv.conf. For instance, no nameservers while
NetworkManager has one in its record (see LP: #1824395):
$ cat /run/resolvconf/resolv.conf
# Dynamic resolv.conf(5) file for glibc
Changed now, thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)
--
You received this bug notification because you are a member of Ubuntu
@sil2100, where can I take a look at those?
--
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/1781597
Title:
[SRU] WoWLAN settings are not supported
Status in
Verified on cosmic, using network-manager 1.12.4-1ubuntu1.2:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename: cosmic
$ apt policy network-manager
network-manager:
Installed: 1.12.4-1ubuntu1.2
Candidate:
@tytso awesome, thanks for pointing out.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1645232
Title:
e2fsprogs - could not preserve ACL permissions : The getxattr()
I am getting this in bionic, with e2fsprogs 1.44.1-1. In fact, I have
tried with e2fsprogs upstream and happens as well. I have simply
followed the instructions in the bug description to reproduce.
So, somewhat, although part of the patch was included upstream, it did
not fix completely the
** Merge proposal unlinked:
https://code.launchpad.net/~awe/network-manager/+git/ubuntu/+merge/352119
--
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/1780606
The patch has been included in Debian klibc package 2.0.4-12:
http://metadata.ftp-
master.debian.org/changelogs/main/k/klibc/klibc_2.0.4-12_changelog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
** Summary changed:
- WoWLAN settings are not supported
+ [SRU] WoWLAN settings are not supported
--
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/1781597
Title:
Public bug reported:
[Impact]
WoWLAN lets us wake up the system by sending wake packages over the wifi
connection. This is something requested by some OEM projects, for bionic
server images.
NM 1.12 supports configuring this feature, so this can be achieved by
backporting that support to 1.10
Public bug reported:
WHen I get into google or some other programs, my screen fails, and
don't work any longer. It became a screen like that of the Tv shows when
there is not signal, and it just doesn't respond any more. I can't do
anything, and I must restart the PC, the screen doesn't allow me
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1725190
Title:
Please update
I have tried the packages in xenial-proposed for two modems:
Sierra HL8548
ZTE MF626
I was able to connect and everything seemed to be working as expected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in
** Description changed:
- Since linux-4.4.0-98, the kernel additionally load gcserial driver for
+ [Impact]
+
+ * Dell Wireless DW5818/5819 modems showed an incorrect signal strength
+ and were using a ttyUSB* port for data connections instead of the MBIM
+ device (which provides better
@Lukasz please go for sponsoring the zesty->xenial backport, that is
enough to get support for the original modem OEM enablement needed. The
work in the patches needs some time, so better do this for the moment.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
@Lukasz those are patches for Dell modems (plano project, unbuntu core).
It makes sense to upstream some of them in fact, and that is something I
can try.
But, it would still make sense to backport the zesty packages to xenial,
as that has the support needed for DW5816e (lp #1693756). If you
@Lukasz, I uploaded the backported packages (zesty->xenial) + patches
from the snap in:
https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/modem-
manager-backport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@Lukasz yes, I think that using the version in zesty is perfectly
feasible, I can prepare the packages for that. About using the backports
pocket, I will let YC or Alex comment on that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Packages uploaded to https://launchpad.net/~snappy-hwe-
team/+archive/ubuntu/stacks-overlay and built for xenial. The versions
are the same as for artful, plus additional patches for Dell modems in
the modem-manager source package.
--
You received this bug notification because you are a member
** Description changed:
We would like to upgrade xenial to 1.6 series so it supports the same
- modems as the modem-manager snap, specifically some new Sierra modems.
- These are the packages that would need to be updated:
+ modems as the modem-manager snap, specifically some new Sierra modems
After chatting with sil2100, he said that potentially we could backport
artful 1.6.8 modemmanager to xenial, which would be great. I have
created bug #1725190 to track that and start in a clean state from
there.
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
We would like to upgrade xenial to 1.6 series so it supports the same
modems as the modem-manager snap, specifically some new Sierra modems.
These are the packages that would need to be updated:
libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
libqmi: 1.12.6-1 in xenial,
It looks like both upstream and debian are not being responsive, looks
like klibc has no maintainer in neither of those. Should we add this
patch to the Ubuntu package?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in
*** This bug is a duplicate of bug 1623125 ***
https://bugs.launchpad.net/bugs/1623125
@smb, actually, there is no create time field in the fs header, see
http://paste.ubuntu.com/25478756/
(this comes from a file with the mount time already corrected). This is
a partition created with
@smb the concrete problem this was solving was happening with an armhf
device running Ubuntu Core. UC assertions were not validated and a
system user could not be created if there was no network (no date
update). Not sure if this was breaking the system even if later you
connected the device.
--
@smb what I have seen is that devices lacking RTC battery tend to never
had a good date in the "last mount day" date of the root filesystem, as
when root is mounted the date is always near the epoch. The patch can
correct this, otherwise we would be getting the date systemd was built.
Of course
Public bug reported:
it got stuck in login page, only reinstalling drivers helped, but my
screen looks too different.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: initramfs-tools 0.103ubuntu4.7
ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-lowlatency 4.2.8-ckt1
Uname: Linux
New patch version, which includes now a patch from ogra (LP: #1623125)
** Patch added: "fixrtc-changes.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+attachment/4893078/+files/fixrtc-changes.patch
--
You received this bug notification because you are a member
This is the output of dumpe2fs:
http://paste.ubuntu.com/24815516/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1696981
Title:
fixrtc is ineffective when there
This debdiff adds a fixrtc-mount that helps with this issue by looking
at dates from files, once root has been mounted.
** Patch added: "add-fixrtc-mount.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+attachment/4893067/+files/add-fixrtc-mount.patch
--
You
Public bug reported:
When there is no battery for the RTC, fixrtc is not able to find a good
enough date. To fix the clock, this script is using the last time the
root filesystem was mounted, but as that is done before there is any
network, and as after a reboot/poweroff the RTC time is always
I'm beeing asked to re-install apport 2.20.1-0ubuntu2. How do I do that?
--
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/1696126
Title:
package apport 2.20.1-0ubuntu2.6
Public bug reported:
none
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportLog:
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
libtasn1-6: Install
apport:
Reported to debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=863761
** Bug watch added: Debian Bug tracker #863761
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863761
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Add a slightly modified version of the patch.
** Patch added: "add-reboot-argument-support.patch"
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+attachment/4883202/+files/add-reboot-argument-support.patch
--
You received this bug notification because you are a member of
Public bug reported:
... so we cannot do things like "reboot recovery" in devices that follow
the Android partitions conventions.
** Affects: klibc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Patch added: "add-reboot-argument-support.patch"
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+attachment/4881283/+files/add-reboot-argument-support.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Fix released in Debian?
Reading the bug report (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=711341) they just closed it with a wontfix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
I have tested the package in yakkety and fixed the issue for me too. In
my case it appeared when switching wifi connection between two APs which
shared the DHCP server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq
** Attachment added: "unity-system-compositor.log"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1664994/+attachment/4819575/+files/unity-system-compositor.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
When I log in into unity8 I get a black screen.
This is happening on xenial+overlay, using the unity8 snap. It seems to
have started to happen after doing a dist-upgrade which installed
packages from the overlay (15 Feb).
Installed snaps:
$ snap list
Name
This is an issue for me too. The use case is media-hub on desktop. We
render into a framebuffer object and pass the textures to other process
(mediaplayer-app usually) that renders them in a window. We obviously do
not want a window shown by media-hub-server, but we need to connect to
mir to
PR proposed with the patch:
https://code.launchpad.net/~alfonsosanchezbeato/ubuntu/+source/gst-
plugins-bad1.0/+git/gst-plugins-bad1.0/+merge/314513
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
@d.filoni, you can find gstreamer0.10 and qtmultimedia packages in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2147
Please give the silo a try and let us know if things work as expected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@d.filoni oh, I see, there is some glue code missing in qtmultimedia in
all versions. That needs landing in xenial too indeed :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in Ubuntu.
Another note: playing opus works just fine because the code path in that
case goes through qtmultimedia -> qtubuntu-media -> media-hub ->
gstreamer 1.0.
So the missing thing is opus encoding in vivid for
qtmultimedia/gstreamer 0.10, and that is what Devid's patches fix.
--
You received this bug
@timo-jyrinki regarding whether this is fixed in xenial or newer:
1. xenial uses qtmultimedia 5.5.1, which depends on gstreamer1.0
2. gstreamer1.0 moved the opus[dec|enc] codecs to plugins-base in version 1.8,
which is included by default in phone images
So yes, this should be solved in xenial
1 - 100 of 351 matches
Mail list logo
