Seems resolved.
** Changed in: file (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/2059723
Title:
Please delete libmagic1
Same problem is back now that 1:5.45-3build1 is uploaded and 1:5.45-2
still isn’t deleted.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/2059723
Title:
Please delete
It seems like 1:5.45-3 was deleted instead of 1:5.45-2? That resolves
the immediate issue, I guess, but it’s probably not the intended
resolution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
Public bug reported:
As part of the 64-bit time_t transition, libmagic1 was renamed to
libmagic1t64 in https://bugs.debian.org/1063113. However, libmagic1
1:5.45-2 is still in the archive, despite being non-installable:
# apt-get install libmagic1
Reading package lists... Done
Building
This new sysconfig-debian-schemes.diff has broken virtual environments
(venv and virtualenv). Please take a look at the fix in
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
*** This bug is a duplicate of bug 1951279 ***
https://bugs.launchpad.net/bugs/1951279
** This bug has been marked a duplicate of bug 1951279
OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: openssh (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/47958
Title:
ssh-agent clobbers LD_LIBRARY_PATH
** Bug watch added: Debian Bug tracker #929417
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417
** Also affects: debconf (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417
Importance: Unknown
Status: Unknown
** Also affects: debconf (Ubuntu)
The situation with apache2 is what I documented in
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:
“But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454. (As you can see, this
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1792745
Title:
NetworkManager
1.12.4 is in cosmic-proposed now with the upstream fix.
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: network-manager (Ubuntu)
Assignee: Anders Kaseorg (andersk) => (unassigned)
--
You received this bug notification becau
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Anders Kaseorg (andersk)
** Tags added: patch
** Patch added: "rebased on 1.12.2-0ubuntu5"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5192582/+files/network-manager_1.12.2-0ubuntu5_lp1792745.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
--
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/1792745
Title:
NetworkManager crashed with SIGSEGV in _int_malloc()
Status in NetworkManager:
Unknown
Status in
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5191867/+files/network-manager_1.12.2-0ubuntu4_lp1792745.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Bug watch added: GNOME Bug Tracker #797136
https://bugzilla.gnome.org/show_bug.cgi?id=797136
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=797136
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Likewise, nginx does not support PCRE2:
https://trac.nginx.org/nginx/ticket/720
** Bug watch added: trac.nginx.org/nginx/ #720
http://trac.nginx.org/nginx/ticket/720
** Changed in: nginx (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
Note to those filing upstream bugs: probably don’t call the old library
“pcre3” since that’s not a thing outside Debian/Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
I think that completes the analysis of the current state of things.
Although it seems infeasible to demote PCRE at this time, there’s no
reason that should block the promotion of PCRE2, especially seeing as a
bundled copy of PCRE2 is already in main (18.04 and 18.10) via
libqt5core5a.
** Changed
• Quagga: no PCRE2 support
• Rasqal: no PCRE2 support
• S-Lang: no PCRE2 support
** Changed in: quagga (Ubuntu)
Status: New => Incomplete
** Changed in: rasqal (Ubuntu)
Status: New => Incomplete
** Changed in: slang2 (Ubuntu)
Status: New => Incomplete
--
You received this
• pam_mount: no PCRE2 support
• nmap: no PCRE2 support
• postfix: no PCRE2 support,
http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
• pyScss: no PCRE2 support
** Changed in: libpam-mount (Ubuntu)
Status: New => Incomplete
** Changed in: nmap (Ubuntu)
• Aide: no PCRE2 support
• Exim: no PCRE2 support, upstream bug:
https://bugs.exim.org/show_bug.cgi?id=1878
• FreeRADIUS: no PCRE2 support, mentioned in passing:
https://github.com/FreeRADIUS/freeradius-server/issues/1865
• GLib: no PCRE2 support
• grep: no PCRE2 support
** Bug watch added:
Copying from
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20,
HAProxy and SELinux upstream support PCRE2.
https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b
Andreas: No, it’s not a bug. PCRE2 is a new project that’s not intended
to be compatible with the older PCRE (i.e. what Debian misnamed
“pcre3”). The API is completely different and this is expected. See
bug 163 for context, and specifically the PCRE2 release announcement
linked in the bug
apr-util has a false Build-Depends on libpcre3-dev; it should simply be
dropped. A corresponding Depends was already dropped in
https://bugs.debian.org/757140.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
It seems suspicious that cb_data->concheck.curl_ehandle is cleaned up
here despite the comment a few lines above warning that it’s unsafe to
do so.
https://github.com/NetworkManager/NetworkManager/blob/1.12.2/src/nm-
connectivity.c#L190-L213
/* Contrary to what cURL manual claim
Here’s a valgrlind log showing many invalid writes to freed addresses in
cb_data_free → curl_multi_remove_handle and nm_connectivity_check_start
→ curl_multi_add_handle, which could explain the heap corruption.
** Attachment added: "nm.19802.log"
** Information type changed from Private to Public
--
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/1792745
Title:
NetworkManager crashed with SIGSEGV in
Older versions in bionic than in xenial, as of now:
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
linux-meta-azure 4.15.0.1021.21 < 4.15.0.1021.27
linux-meta-gcp 4.15.0.1017.19 < 4.15.0.1017.29
** Summary changed:
- Older version in artful than in xenial
+ Older version in bionic
** Description changed:
These packages have an older version in artful than in xenial.
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 <
Until this is uploaded to bionic, the version in bionic is older than in
xenial (bug 1780680), which is going to interfere with upgrades.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
These packages have an older version in artful than in xenial.
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
patch
** Changed in: console-setup (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt-f2 switches to virtual
Just because DISPLAY isn’t set for the current process doesn’t mean X or
Wayland aren’t running. For example:
pkexec env DEBIAN_FRONTEND=noninteractive dpkg-reconfigure keyboard-
configuration
still triggers this bug (because pkexec does not propagate environment
variables), and you can imagine
On my bionic system, I had to manually remove resolvconf on account of
bug 1713457. I think it was not being autoremoved because other
packages like isc-dhcp-client, pppconfig, vpnc-scripts have Suggests:
resolvconf.
So I don’t think I’m seeing this particular issue. However, the lack of
Verified using ubuntu-17.04-desktop-amd64.iso.
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Public bug reported:
When I connect to a wireless network that sets a DNS search domain name
via DHCP, the line 'search ' is added to /etc/resolv.conf as
expected. But if I then disconnect and connect to a different network,
it is not removed from resolv.conf. If the second network also sets a
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
Importance: Unknown
Status: Unknown
** Changed in: systemd
Importance: Unknown => Undecided
** Changed in: systemd
Status: Fix Released => New
** Changed in: systemd
Remote
Ping? It’s still really frustrating to have the entire system go
unresponsive for a minute just because gnome-shell crashed and apport
won’t let it restart until it’s finished compressing the core dump.
If you’re not willing to go all the way to zlib level 1, can we at least
proceed with going
In fact, having recently disabled FallbackDNS for myself, I find that I
get no DNS at all maybe a quarter of the time I reboot my system. This
suggests that systemd-resolved might be silently relying on the 8.8.8.8
fallback much more often than even I suggested above.
Can we try disabling
Dimitri: It is not merely difficult, but in fact fundamentally
impossible, to make everyone use nss_resolve for DNS resolution. Many
programs cannot use nsswitch for DNS at all. This includes anything
that needs to lookup record types other than A and (e.g. SRV, TXT,
MX, SSHFP, AFSDB),
Martin, was the DNSSEC=allow-downgrade default not switched off for the
17.04 stable release like you said it would?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Ah, zesty still has 232-19 but this is presumably fixed in zesty-
proposed’s 232-21ubuntu1.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Public bug reported:
If you are running ‘journalctl -f’ to try to debug some other problem,
you are constantly interrupted by zillions of these messages from
systemd-resolved:
Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:27 change-mode
Carl: I’m not sure whether that “@Andres” was directed at Andreas or me
(I’m Anders), but I still believe the situation is explained by my
comments #31 and #33; it is not a mystery why this is seen only
occasionally. The bug is triggered every time the console-setup package
is installed or
Steve: I didn’t test yakkety since I thought it had gone back to the
configuration with dnsmasq on 127.0.0.1 rather than systemd-resolved on
127.0.0.53. If that’s not the case, then yeah, it would be affected
too.
--
You received this bug notification because you are a member of Ubuntu
Touch
Ognjen, Vincent: This bug is marked with the “resolved” _tag_, as in
“systemd-resolved”, not as in “fixed”. The bug _status_ is still open
(Confirmed).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Or virtual machines: a VM running in virt-manager on a zesty host can’t
resolve CNAMEs (not even a zesty VM with libnss-resolve inside!).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Another case that now necessarily relies on 127.0.0.53 is anything
inside a chroot (e.g. sbuild). libnss-resolve can’t help there: you
can’t talk to the host D-Bus from inside, and also you might want to
chroot a distro that’s too old for libnss-resolve anyway.
--
You received this bug
Public bug reported:
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname resolve [!UNAVAIL=return] dns
# apt remove libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files
Whether or not it’s enabled, it is started automatically via D-BUS
activation (/lib/systemd/system/dbus-org.freedesktop.resolve1.service ->
systemd-resolved.service).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Firefox, wget, ping, and Chrome do not work unless libnss-resolve is
installed. (Perhaps Chrome recently started using NSS in some cases?)
Maybe this isn’t quite as critical as I thought given that ubuntu-
standard Recommends libnss-resolve. Still, it’s not just an
“implementation detail”. DNS
Martin: I still wonder what the point of having resolvconf is, if it’s
only ever supposed to be used to manage 127.0.0.53, and every other use
of resolvconf will lead to this bug resurfacing. I still propose that
systemd-resolved should read from /run/resolvconf/resolv.conf without
adding
Possible duplicate of bug 1647031.
--
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/1647178
Title:
systemd-resolved unable to resolve certain subdomains
Status in systemd
For example, I see
$ dig +no{cmd,comments,stats} mail.google.com @8.8.8.8
;mail.google.com. IN A
mail.google.com.86312 IN CNAME googlemail.l.google.com.
googlemail.l.google.com. 212IN A 216.58.219.229
$ dig +no{cmd,comments,stats} mail.google.com
Possible duplicate of bug 1647031. For example, I see
$ dig +no{cmd,comments,stats} buy.ubuntu.com @8.8.8.8
;buy.ubuntu.com.IN A
buy.ubuntu.com. 599 IN CNAME
ubuntu-advantage-cloud-guest.myshopify.com.
ubuntu-advantage-cloud-guest.myshopify.com.
** Patch added: "Debdiff from vim 2:8.0.0095-1 in Debian testing/unstable"
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1647105/+attachment/4787466/+files/vim_8.0.0095-1_1ubuntu1.debdiff
** Patch removed: "Debdiff from vim 2:8.0.0095-1 in Debian testing/unstable"
*** This bug is a duplicate of bug 1647105 ***
https://bugs.launchpad.net/bugs/1647105
** This bug has been marked a duplicate of bug 1647105
Merge vim 2:8.0.0095-1 from Debian testing/unstable
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
Since Debian has now migrated vim from Python 2 to Python 3, this drops
the Python 2 variants.
Test build: https://launchpad.net/~andersk/+archive/ubuntu/ppa
** Affects: vim (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
** Patch added: "Debdiff
Public bug reported:
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping
Upstream applied an equivalent patch:
http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=e1164591f7927402af8d73d340e75dbfeb06a288
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
Upstream submission: http://marc.info/?l=util-linux-
ng=147691687505965=2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1577460
Title:
mkinitramfs --help > Core
This is a util-linux bug, not a glibc bug. I have sent this patch
upstream.
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Patch added:
"0001-getopt-Terminate-long_options-even-if-add_long_optio.patch"
The 8.8.8.8 fallback is not only used on misconfigured systems! It’s
also used for a short period while initially connecting or reconnecting
to totally healthy networks with DHCP. So the excuse that privacy-
conscious users should just use DHCP holds no water.
** Tags removed: regression-release
--
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/1624317
Title:
systemd-resolved breaks VPN with split-horizon DNS
Status in systemd:
** Description changed:
On the MIT network (which runs some ancient version of BIND 9), systemd-
resolved stops resolving anything that isn’t DNSSEC-signed after I
disconnect and reconnect the network. Signed zones continue to resolve.
This happens with either DNSSEC=yes or the default
Public bug reported:
On the MIT network (which runs some ancient version of BIND 9), systemd-
resolved stops resolving anything that isn’t DNSSEC-signed after I
disconnect and reconnect the network. Signed zones continue to resolve.
This happens with either DNSSEC=yes or the default
** Tags added: regression-release
** Tags added: yakkety
--
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/1624317
Title:
systemd-resolved breaks VPN with split-horizon DNS
I want to be clear that in my situation the VPN’s DNS servers are _not_
marked as domain-restricted.
--
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/1624317
Title:
(I believe the requested information has been provided.)
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
DNS resolution outside NSS shouldn’t be dismissed as an edge case for
software that’s too conceited to use NSS. NSS only exposes A, , and
PTR records. There’s plenty of software in the official archive that
needs other records from DNS (off the top of my head: SRV, TXT, MX,
SSHFP, AFSDB) and
3421 seems like the opposite of this problem. There, queries that
belong on the local network instead go to the domain-limited VPN
servers. Here, queries that should go to the VPN servers (which in my
case are not domain-limited) instead go to the local servers. Also,
here I am using
Public bug reported:
systemd-resolved, or more precisely the hook script /lib/systemd/system
/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add
127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the
other nameservers. That makes no sense because
Public bug reported:
I use a VPN configured with network-manager-openconnect-gnome in which a
split-horizon DNS setup assigns different addresses to some names inside
the remote network than the addresses seen for those names from outside
the remote network. However, systemd-resolved often
Filed https://github.com/systemd/systemd/issues/4157 upstream for the
NOTFOUND vs. UNAVAIL problem.
** Bug watch added: github.com/systemd/systemd/issues #4157
https://github.com/systemd/systemd/issues/4157
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Description changed:
The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the
hosts line of /etc/nsswitch.conf. This makes DNSSEC validation
impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because
if libnss_resolve returns a validation failure, glibc
You’re right: glibc seems to treat the absence of libnss-resolve itself
as UNAVAIL, which is the same code returned on DNSSEC validation
failures when libnss-resolve is working. I don’t see a way around this
other than patching libnss-resolve to return NOTFOUND (or TRYAGAIN?) on
validation
I also worry that, by masking systemd-resolved failures, this fallback
has meant that systemd-resolved is not really getting adequate testing.
If there were widespread problems causing systemd-resolved lookups to
fail, would anyone have noticed?
--
You received this bug notification because you
Public bug reported:
The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the
hosts line of /etc/nsswitch.conf. This makes DNSSEC validation
impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because
if libnss_resolve returns a validation failure, glibc will simply
I’m running Ubuntu Gnome 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt-f2 switches to virtual terminal 2
Status in console-cyrillic
When console-setup is configured, it runs ‘setupcon --force’, which
breaks the running X server in exactly this way.
** Also affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This might have something to with the default setting
ACTIVE_CONSOLES="/dev/tty[1-6]" in /etc/default/console-setup
conflicting with the recent move of X from console 7 to console 2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Level 5 isn’t crazy, though it’s still some 70% slower than level 1.
zlib.compressobj(level=1) time=7.6 size=84869397
zlib.compressobj(level=2) time=7.8 size=82465461
zlib.compressobj(level=3) time=8.4 size=79576183
zlib.compressobj(level=4) time=12.2 size=74672475
zlib.compressobj(level=5)
Public bug reported:
When apport takes a core dump of a large application, it uses 100% CPU
for a _long_ time (often 30 seconds or more) to compress the core dump.
The system is virtually unusable during this time, especially if the
application was the window manager and won’t be restarted until
** Bug watch added: Python Roundup #25493
http://bugs.python.org/issue25493
** Also affects: python via
http://bugs.python.org/issue25493
Importance: Unknown
Status: Unknown
** Bug watch added: GNOME Bug Tracker #757184
https://bugzilla.gnome.org/show_bug.cgi?id=757184
**
This is a combination of two problems. One is that starting update-
manager results in these warnings:
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to ensure
that the right version gets loaded.
I did not write the fix, but you should be checking the 1.0.2 manpages,
not the 1.0.1 manpages.
--
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/1489050
Title:
Option
Public bug reported:
$ zcat /usr/share/doc/openssl/changelog.gz
gzip: /usr/share/doc/openssl/changelog.gz: No such file or directory
$ ls -l /usr/share/doc/openssl/changelog.gz
lrwxrwxrwx 1 root root 27 Jul 9 10:06 /usr/share/doc/openssl/changelog.gz -
../libssl1.0.0/changelog.gz
$ ls -l
Fixed in OpenSSL 1.0.2 in wily.
** Changed in: openssl (Ubuntu)
Status: Confirmed = Fix Released
--
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/1489050
Title:
You might think that, but in fact the hook shipped with btrfs-tools only
copies in /bin/fsck.btrfs if /usr/share/initramfs-tools/hooks/fsck is
not executable. It is executable, so this has no effect.
I have checked on current wily with / on btrfs that my initramfs really
is missing fsck.btrfs (in
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1482439
Title:
wpa_supplicant crashed with SIGSEGV in
Public bug reported:
/sbin/fsck.btrfs moved to /bin/fsck.btrfs with btrfs-tools 4.0-2
(http://bugs.debian.org/784234), which causes
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic
Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs,
.xsession is sourced within /bin/sh, not /bin/bash. It wouldn’t make
sense to source .bashrc from it (unless you happened to write a .bashrc
that doesn’t use any bash features).
Also, .bashrc is sourced by _every_ interactive shell, so if you were to add
things to environment variables from
No, you misunderstand my comment. It doesn’t matter whether or not your
shell is bash. ~/.xsession file is sourced using /bin/sh, not using your
shell. You cannot expect to be able to source ~/.bashrc from
~/.xsession, no matter what your preferred shell is.
--
You received this bug notification
Aha, I was confusing ~/.xsessionrc with ~/.xsession. ~/.xsessionrc is
sourced using /bin/sh. A default Ubuntu session does not invoke
~/.xsession at all. Creating one that works correctly with Unity or
GNOME or whatever, as well as configuring LightDM to invoke it it,
requires a very pointy hat.
Public bug reported:
After CVE-2014-8989 was fixed in Linux v3.19-rc1~41, ‘unshare -r’ no
longer works.
$ unshare -Ur
unshare: write failed /proc/self/gid_map: Operation not permitted
$ sudo -i
# unshare -r
unshare: write failed /proc/self/gid_map: Operation not permitted
This was fixed in
** Patch added: Fix by merging util-linux 2.25.2-6 from Debian
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1452099/+attachment/4391896/+files/util-linux_2.25.2-4ubuntu2_lp1452099.debdiff
** Tags added: patch patch-accepted-debian
--
You received this bug notification because
Sure, here it is.
** Attachment added: vmware-USBArbitrator
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1426588/+attachment/4381963/+files/vmware-USBArbitrator
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I can reproduce this message by adding many https repositories to
sources.list. For example, with these sources (which are public, so you
can try this yourself):
deb https://debathena.mit.edu/apt precise debathena
deb-src https://debathena.mit.edu/apt precise debathena
deb
I submitted a patch to https://bugs.debian.org/781509.
** Bug watch added: Debian Bug tracker #781509
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781509
** Also affects: apt (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781509
Importance: Unknown
Status:
1 - 100 of 128 matches
Mail list logo
