Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
** Changed in: apparmor (Ubuntu)
Status: Invalid => Incomplete
** No longer affects: apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1669800
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Qt 5.9.4 is now in bionic-proposed.
** Tags removed: block-proposed
--
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/1749472
Title:
mesa 18.0.0 will cause rendering errors in
It seems that is was a docker host configuration issue.
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Simon Toledano (stoledano)
** Changed in: openssl (Ubuntu)
Status: New => In Progress
** Changed in: openssl (Ubuntu)
Status: In Progress => Fix Released
The bug can be claused.
** Changed in: openssl (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1728608
Title:
"bad record
That would be the ideal way to do it because the fix is already
installable in the CI Train PPA for the next Qt transition:
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3113/+packages
That should be in -proposed before Feature Freeze, if not before then.
Is there a compelling
Public bug reported:
From
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1749931/comments/4:
[2794367.925181] apparmor="DENIED" operation="open"
profile="/usr/sbin/unbound" name="/var/lib/sss/mc/initgroups" pid=5111
comm="unbound" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
The
\o/
--
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/1746807
Title:
18.04 daily installer fails missing kernel
Status in apt package in Ubuntu:
Fix Released
Bug
block-proposed still belongs for mesa, having it blocked for other
reasons isn't good enough because this bug will break the Kubuntu and
Lubuntu Next desktops.
** No longer affects: qtbase-opensource-src (Ubuntu Bionic)
** No longer affects: qtbase-opensource-src (Ubuntu)
** Tags added:
I just manually triggered a rebuild for Lubuntu Alternate since this
landed, and after that, things should be good.
Thanks everyone!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I did a git bisect on the source and it identified this upstream commit
as being the potential culprit: https://salsa.debian.org/apt-
team/apt/commit/1adcf56bec7d2127d83aa423916639740fe8e586
I can confirm that this is the culprit by testing the output of `apt-
cdrom add` before and after
(to be more specific, here's a link to the exact line:
https://salsa.debian.org/apt-
team/apt/commit/1adcf56bec7d2127d83aa423916639740fe8e586#41c542e857179bd3fe055e92c64389379fb23e75_65_65
)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
I would like to reference the fact that CC0-1.0 has been moved to
common-licenses in a package I'm working on. Please merge base-files
10.1 from Debian so this statement can be accurate.
** Affects: base-files (Ubuntu)
Importance: Undecided
Status: New
--
You
Public bug reported:
Ubuntu's cron version doesn't support setting MAILFROM to set the
"From:" header of cron generated emails. This feature would be nice to
have and bring parity with RHEL/CentOS which has it since RHEL 6:
$ cat /etc/redhat-release
CentOS release 6.6 (Final)
$ man 5 crontab |
** Changed in: sddm (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1668722
Title:
60x11-common_xdg_path uses
)
Importance: Undecided
Status: New
** Changed in: xorg (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: xorg (Ubuntu Bionic)
Importance: High => Wishlist
** Changed in: xorg (Ubuntu Bionic)
Assignee: Simon Quigley (tsimonq2) => (unassigned)
** Changed
** Changed in: lxsession (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: lxsession (Ubuntu)
Milestone: None => ubuntu-18.02
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Changed in: lxsession (Ubuntu)
Status: New => In Progress
** Changed in: lxsession (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Changed in: xorg (Ubuntu Bionic)
Milestone: None => ubuntu-18.02
--
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/1668722
Title:
60x11-common_xdg_path uses
** Changed in: xorg (Ubuntu)
Importance: Undecided => High
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Tags added: rls-bb-incoming
--
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/1668722
Title:
60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check
Status
** Tags removed: rls-bb-incoming
--
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/1668722
Title:
60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check
Status
> Gunnar, Kubuntu and Lubuntu Next are free to install fonts-symbola if
they want. (But they should really talk to Qt about getting color emoji
support working everywhere too!)
I don't think that's the point; if we're talking about inclusion in
desktop-common, support for Qt *and* GTK needs to be
I agree with Gunnar, I'm -1 with both my Lubuntu and Kubuntu hats on if
this means a regression for Qt-based desktops.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
Oh, sorry about that. Apparently, xterm uses a different value for PS1
than gnome-terminal by default. It seems that this issue only happens
when color escape sequences are involved, which is why it didn’t happen
for me in xterm. However, when I manually set xterm to the same value as
in
My locale is as follows:
$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
As a quick update, it does seem to be bash that crashes – see the
following terminal session:
user@host:~$ sh
$ cd
/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789/
$ bash
Segmentation
Public bug reported:
When I try to play a file in Rhythmbox. I get a "Thump" sound and a pop-
up message that it can't connect to gstreamer.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-109.132-powerpc-smp 4.4.98
Bump, was anything done with this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1715931
Title:
Update to exiv2 version 0.26
Status in exiv2 package in Ubuntu:
Triaged
Xenial ships 1.5.6-2 so marking as fix released.
** Changed in: xmltooling (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
c-smp 4.4.98
Uname: Linux 4.4.0-109-powerpc-smp ppc
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: powerpc
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: simon 2322 F pulseaudio
CurrentDesktop: MATE
Date: Tue Jan 16 23:10:57 2018
InstallationDate: Ins
4
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-109.132-powerpc-smp 4.4.98
Uname: Linux 4.4.0-109-powerpc-smp ppc
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: powerpc
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: simon 2322 F pulse
I feel like an ack/nack from the SRU Team before sponsoring would be
preferred, given that this is a bit of a special case. Subscribed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
Pretty much every single one that would do a hostname lookup it seems.
Tried ping, ping6, nc, wget; they all crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1723956
Sure, here we go. It might be worth to note that this system was
installed as 12.04 or 12.10 and dist-upgraded ever since, so maybe this
would explain some oddities, although in general everything works just
fine.
libc6:
Installed: 2.24-9ubuntu2.2
Candidate: 2.24-9ubuntu2.2
Version table:
On a hypervisor, binding on link local IPs is undesirable IMHO and
that's why I always added a similar ignore to the one you proposed. That
said, NTP works well over link local addresses so some folks are
probably using it.
--
You received this bug notification because you are a member of Ubuntu
Hello Christian,
On 2017-12-11 10:36 AM, ChristianEhrhardt wrote:
> Hi Simon,
> we are currently shuffling around responsibilities for iproute so extra
> latencies might occur :-/.
I have no urgent need for this. I was simply experimenting with an
IPv6-only lab.
> 2. the Xenia
Public bug reported:
[Impact]
Xenial users are unable to create vti6 tunnels.
[Test case]
1) Create a vti6 tunnel
sudo ip tunnel add vti0 mode vti6 local :: remote fdd6:bdb4:5614::2 key 54
2) No error should be displayed and "ip link" should show a new device named
"vti0"
The ip tunnel call
Steve, so I just manually gather a core dump and attach it here? I
assumed this is what apport is for. I uploaded the crash report using
the standard crash report window that pops up when I opened the issue.
Do they just go straight to /dev/null instead of the maintainers?
** Attachment added:
Public bug reported:
tried to restart service, It would not restart. fails on every reboot
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor 2.10.95-0ubuntu2.7
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
NonfreeKernelModules: wl
Thanks for the patch Christian, I relayed it in https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=882556
** Bug watch added: Debian Bug tracker #882556
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882556
--
You received this bug notification because you are a member of Ubuntu
Touch
A possible workaround would be to add "Restart=on-failure" in the
"[Service]" section of the systemd unit.
--
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/1689833
Title:
** Also affects: steam (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to
** Changed in: patch (Ubuntu)
Assignee: Simon Vall (svsimonvall) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to patch in Ubuntu.
https://bugs.launchpad.net/bugs/1690861
Title:
typo of descripi
** Branch unlinked: lp:~svsimonvall/+junk/patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to patch in Ubuntu.
https://bugs.launchpad.net/bugs/1690861
Title:
typo of descripiton in README
Status in Patch:
Unknown
** Branch linked: lp:~svsimonvall/+junk/patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to patch in Ubuntu.
https://bugs.launchpad.net/bugs/1690861
Title:
typo of descripiton in README
Status in Patch:
Unknown
Status
** Changed in: patch (Ubuntu)
Assignee: (unassigned) => Simon Vall (svsimonvall)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to patch in Ubuntu.
https://bugs.launchpad.net/bugs/1690861
Title:
typo of descripi
Public bug reported:
Using openssl 1.0.2g inside a docker container generated from
ubuntu:xenial, it seems impossible to connect to a SSL socket. The
client side always report a "bad record mac" and closes the connection.
The following information should help to reproduce the issue:
lib/firefox/firefox{,*[^s][^h]} simon 19556 33.1 2.1 773068 168052
pts/5 Sl+ 10:11 0:03 /usr/lib/firefox/firefox
https://help.ubuntu.com/10.04/serverguide/serverguide.pdf
/usr/lib/firefox/firefox{,*[^s][^h]}//sanitized_helper simon 19586 19.6 0.4
561964 37176 pts/5 Sl+ 10:11 0:00 evince /
F through Evince:
1) firefox https://help.ubuntu.com/10.04/serverguide/serverguide.pdf
Observe the Apparmor profiles loaded:
2) ps Zaux| grep -v ^unconfined
/usr/lib/firefox/firefox{,*[^s][^h]} simon 19556 33.1 2.1 773068 168052
pts/5 Sl+ 10:11 0:03 /usr/lib/firefox/firefox
https://help.u
I'm no longer working there so it's not very important to me anymore. I
suppose if somebody still needed this fix they would have made a comment
here by now... With 18.04 around the corner I imagine desktop usage of
14.04 isn't very applicable anymore.
--
You received this bug notification
Public bug reported:
On a fully up-to-date Ubuntu 17.04, running most applets from busybox-
static that are network-related lead to a segfault. Example:
$ busybox nslookup google.com 8.8.8.8
Server:8.8.8.8
Segmentation fault
$ busybox
BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2)
Thanks for the kernel bugzilla link, Dik, its power-save saving
suspicion seems valid, at least now I had a full day of uptime without
this wifi failure.
So, for anyone else who also wants to give it a try:
1. If you are using NetworkManager, then check
The same here, "Error sending C_SCAN: enqueue_hcmd failed" and "BSM
uCode verification failed at addr" and all the other niceties, for this
good ol' piece of hw that have been working flawlessly under other OSes,
so it's definitely a sw issue.
I don't really hope for getting a solution, but
** Also affects: wayland (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1720901
Title:
VLC under Wayland causes
* Changed in: abiword (Ubuntu Xenial)
Status: In Progress => Confirmed
** Changed in: abiword (Ubuntu Artful)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: abiword (Ubuntu Zesty)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received thi
Ok, did you get a chance to test it or did you just review the diff?
--
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
Since Wayland is not supported by Lubuntu, the only flavor that ships it
by default, and stock Ubuntu has their own replacement, I'm willing to
have this fix in Ubuntu.
I uploaded a fix to ppa:tsimonq2/universe-upload-testing. It would be
great if someone could test it and if it works, I'll
** Changed in: abiword (Ubuntu Xenial)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: abiword (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Same case than Gannet after Zesty upgrade. Disabling DNSEC does not fix
anything.
--
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/1609546
Title:
DNS lookup through Netgear
** Changed in: network-manager (Ubuntu)
Assignee: Simon Quigley (tsimonq2) => (unassigned)
** Summary changed:
- Kubuntu 16.04 requires that the wifi password be entered twice before wifi
can be used
+ Kubuntu requires that the WiFi password be entered twice before WiFi can be
u
** Description changed:
+ [Impact]
+
+ It's impossible to build gdebi from source with the locale other
+ than en_US in Trusty.
+
+ It had been fixed in gdebi 0.9.5.5, which is available in newer
+ releases, starting from Vivid. The backported fix can be applied
+ in Trusty.
+
+ The debdiff
I see the NM one passes now, thanks for retrying it. The aria2 armhf
problem reliably fails though. I guess I'll have to setup a QEMU VM for
that arch and manually run the test to see what's going on.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
@juliank, thanks for the update. I wasn't aware of the autopkgtest
failing for some reverse dependencies. Any pointers to those? I'm
determined to see this one though, but on Monday ;)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The Xenial fix is identical to what went in Artful and Zesty so it
shouldn't be subject to any more review.
The review was requested to check if the different fix proposed for
Trusty was OK.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
It's been a while since the Xenial -proposed package have been
successfully validated. Is there anything preventing it from entering
-updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnutls26 in Ubuntu.
@Jeremy:
If you get a Feature Freeze Exception as defined here[1] or an ack from
a member of the release team, I'll be happy to get it uploaded for you.
I want to upload your patches, I just don't want to break freeze and
have to apologize to the release team... sorry. :/
[1]
The Lubuntu Software Center has not been updated for several cycles and
we don't even ship with it by default any more.
On behalf of the Lubuntu Team, I'd like to request that src:lubuntu-
software-center be removed from Artful. Subscribing the Archive
Administrators Team.
Reverse depends:
$
It doesn't seem like Fedora Rawhide has any (new) patches modifying
poppler at all: https://src.fedoraproject.org/rpms/poppler/tree/f27
There also doesn't seem to be any relevant patches in the Ubuntu
packaging...
Otherwise, I can reproduce.
--
You received this bug notification because you
(in any case, we're already in Feature Freeze, so unless an exception is
given (in which case I'll gladly upload it), it's too late to go in
Artful)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ncurses in Ubuntu.
Oh, I apparently don't know how to read...
Thanks Mattia!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ncurses in Ubuntu.
https://bugs.launchpad.net/bugs/1637239
Title:
Please merge ncurses 6.0+20161126-1 (main) from
Unfortunately it doesn't look like it made it in in time for Feature
Freeze... a Feature Freeze Exception can be written, otherwise this will
have to wait until next cycle.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Unsubscribing ~ubuntu-sponsors as there isn't an updated patch yet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1695876
Title:
German Documentation file displays
Hello Paulo!
Could you please be more specific as to what Ubuntu release this
affects? Also, could you please provide a debdiff with a patch under
debian/patches?
Please feel free to resubscribe ~ubuntu-sponsors when you have an
updated patch.
Thank you!
--
You received this bug notification
Unsubscribing ~ubuntu-sponsors as this has been uploaded already.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ncurses in Ubuntu.
https://bugs.launchpad.net/bugs/1637239
Title:
Please merge ncurses 6.0+20161126-1 (main)
Uploaded to Xenial, it's in the Unapproved queue now.
Unsubscribing ~ubuntu-sponsors as there's nothing left to do. Feel free
to resubscribe ~ubuntu-sponsors if this was done in error.
Thank you for your contribution to Ubuntu!
--
You received this bug notification because you are a member of
801 - 900 of 1674 matches
Mail list logo
