** Changed in: juju
Status: Triaged => In Progress
** Changed in: juju
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
no matching
Literally just toggling that one option "Store password for all users"
in the VPN settings fixes the problem entirely. Use "sudo service
network-manager restart" and it connects flawlessly the first time. To
avoid the error loop on bootup specifically, just uncheck the box "Make
available to other
Yeah, I keep getting the "vpn-connection[...]: Failed to request VPN
secrets #3: No agents were available for this request." error message in
my syslog. I found, however, that THIS worked for me: All you have to do
is go Dash->VPN->VPN
Settings->connection_name_here->Identity->Password->"Store for
Public bug reported:
Kernel 4.13.0-16
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: r8168-dkms 8.044.02-2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: i386
DKMSKernelVersion:
The package works successfully, however, dh_install is missing a file
required for bash completion. We should ensure this file is also copied
to ensure bash completion continues to work for new installs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We've been using and testing against this newer version in our CI for
more than a month without seeing any issues. All normal juju operations
work, and I can connect to the juju database as expected. I tested this
on xenial and zesty.
--
You received this bug notification because you are a
** Tags removed: verification-needed verification-needed-xenial
verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Xenial 16.04.3 on fresh VM, and also exhibited via docker image for
16.04.3.
$ apt-cache policy lldb
lldb:
Installed: 1:3.8-33ubuntu3.1
Candidate: 1:3.8-33ubuntu3.1
Version table:
*** 1:3.8-33ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu
It took a few times, but it looks like it's there now.
Thank you so much for your help.
Nicholas J. Krise
On Sep 20, 2017 1:55 PM, "Andreas Hasenack" <andr...@canonical.com>
wrote:
> Thanks for filing this bug in Ubuntu.
>
> Please try the following commands to see
Public bug reported:
Ubuntu 17.04
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblwres141:amd64 1:9.10.3.dfsg.P4-10.1ubuntu5.2
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
Debian package for network-manager-openvpn-gnome built for Ubuntu 17.04
attached.
** Attachment added: "network-manager-openvpn-gnome_1.2.6-2ubuntu2_amd64.deb"
Debian package for network-manager-openvpn built for Ubuntu 17.04
attached.
** Attachment added: "network-manager-openvpn_1.2.6-2ubuntu2_amd64.deb"
Public bug reported:
This syncs juju with the upstream release bringing the latest bugfixes
and enhancements.
[SRU Information]
juju-core has a stable release exception, including for major version updates,
https://wiki.ubuntu.com/JujuUpdates.
[Impact]
A full list of targeted bugs can be seen
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614969
Title:
Juju packaging allows builds for unsupported
Public bug reported:
i dont know
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CasperVersion: 1.380
Date: Mon Aug 28 15:37:30
Michael, these failed to build on some arches; so looks like they didn't
move into proposed (we are always running proposed). Nevertheless, I've
installed them now onto our xenial and zesty CI slaves so they will run
through the slew of testing now. We'll monitor for regressions.
--
You received
I confirm this issue, LibreOffice Base crushed any time when i try to do
anything in Base. are there any pathches ?
Processor: Intel Pentium T4400 @ 2.20GHz (2 Cores)
Software:
OS: Ubuntu 17.04, Kernel: 4.10.0-26-generic (i686), Desktop: Xfce 4.12, Display
Driver: modesetting 1.19.3, OpenGL:
** Summary changed:
- Remove juju-core from zesty
+ Remove juju-core from artful
** Description changed:
Juju is now releasing as a snap as the primary means of consumption. For
those still needing a debian package the juju ppas will be maintained.
However from a distro perspective, folks
** Changed in: juju-core-1 (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: conjure-up (Ubuntu Xenial)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624914
Title:
juju fails to build on all 32bit architectures
To manage
** Changed in: juju-core-1 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: juju-core (Ubuntu)
Status: In Progress => Fix Released
** Changed in: juju-core-1 (Ubuntu)
Status: Fix Released => Invalid
** Changed in: juju-core (Ubuntu)
Status: Fix Released =>
Please ignore my posts. I now realize it's not the same error. My
apologies. Monitor, please delete my responses. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706128
Title:
package
Though the above is not exactly for 4.4.0-87, 4.4.0-87 is the culprit.
This was a step after the initial issue occurred. If you need additional
logs, please let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In trying to troubleshoot this on a production server I noticed the issue is
actually with linux-image-extra-4.4.0-87-generic. In the apt-auto-remove post
install script, the linux-image-extra-4.4.0-87-generic creates a segfault.
$ sudo apt-get install linux-image-extra-4.4.0-81-generic
Public bug reported:
Instaling subiquity package and running it results in this runtime
error.
2017-07-24 15:00:05,407 subiquity:77 Starting SUbiquity v0.0.5
2017-07-24 15:00:05,407 subiquity:78 Arguments passed: ['/usr/bin/subiquity']
2017-07-24 15:00:05,407 subiquitycore.utils:31 Checking
PS: Here's the log file...
Jul 12 23:38:48 LEE-03 kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0
action 0x6
Jul 12 23:38:48 LEE-03 kernel: ata14.00: irq_stat 0x4001
Jul 12 23:38:48 LEE-03 kernel: ata14.00: cmd
a0/01:00:00:00:01/00:00:00:00:00/a0 tag 1 dma 16640 in
I have also got this bug, but from Ubuntu 16.04.02 LTS (32-bit), (with
MATE desktop add-on)
It would be good if this got some attention, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374595
@Stephan the Penguin god has not forsaken us, my friend :D
So glad it works for you guys, thanks for the nice feedback! This issue bugged
me so much I sorta made it my mission haha. It's fantastic I finally got this
thing sorted out with some help from the Gnome NM devs :)
--
You received this
Please test with the new patch or patched .deb and follow the steps to
set negative ipv4 dns-priority. I (and lead NM-dev Thomas Haller
himself) believe this resolves the bug. Thanks, and I hope this helps
you all! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After setting the ipv4.dns-priority of the VPN connection to a negative number
and patching the source or installing the conveniently packaged .deb below, you
should not experience DNS leaks over NM-VPN.
(Output from extended test at https://dnsleaktest.com )
Test complete
Query round
I have successfully backported Thomas Haller's excellent upstream
solution as detailed in
https://bugzilla.gnome.org/show_bug.cgi?id=783569 This took some time as
things have changed quite a bit upstream, but the patch works on the
current zesty 17.04 1.4.4-1ubuntu3.1 network-manager! This is a
Hey all, so it seems like Thomas Haller at the bug thread
https://bugzilla.gnome.org/show_bug.cgi?id=783569 may have actually
fixed this issue upstream! Not sure how to backport the fix though, I
tried and didn't have any luck, so this may be up to the package
maintainers. I think this might
Unfortunately my patch is not a good solution for upstream application.
I agree with what Beniamino Galvani mentioned, that "it is wrong to
assume the connection is a VPN based on the link type, since you can
have non-VPN tun/tap/gre/gretap connections as well, and they are
affected by this
Actually I take that back. The issue is not fixed by the commit
referenced on https://bugzilla.gnome.org/show_bug.cgi?id=783569 as it is
already present in the current version of the network-manager. So we
still have a major problem folks.
--
You received this bug notification because you are a
My apologies, it seems like this issue could have already been addressed
upstream. See https://bugzilla.gnome.org/show_bug.cgi?id=783569
Anyway, I'll see if I can backport the fix provided there and whether or not it
works. Sorry guys :/
--
You received this bug notification because you are a
I have upstreamed the patch at
https://bugzilla.gnome.org/show_bug.cgi?id=783569 !
Hopefully this can be incorporated into future releases of network-manager :)
** Bug watch added: GNOME Bug Tracker #783569
https://bugzilla.gnome.org/show_bug.cgi?id=783569
--
You received this bug
No, it's not an upstream patch. My patch can be applied directly to the
current source on 17.04 obtained using 'apt-get source network-manager',
so that would be network-manager 1.4.4-1ubuntu3 from
http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
--
You received this bug
In reference to John Bedford's comment:
>bedfojo (commercial-johnbedford) wrote on 2017-06-06: #57
>Nicholas, thank you very much for your work on this patch.
>It works correctly for me: no DNS leak detected by either https://ipleak.net
>or >https://dnsleaktest.com for me, whe
** Attachment added: "patched network-manager .deb for easy testing on Ubuntu
17.04"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4891741/+files/network-manager_1.4.4-1ubuntu4_amd64.deb
--
You received this bug notification because you are a member of
** Patch removed: "patch for network-manager source"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4889747/+files/resolved-vpn-dns-leak-fix.patch
** Patch removed: "possible cisco network-manager-openconnect-fix"
Huh, weird, yeah it's quite possible it's a different issue entirely, or
a problem related to network-manager-openconnect. Because the routing-
only domain is clearly listed as DNS Domain ~. so systemd-resolved
should only send queries to the specified dns servers for the interface
vpn0.
Huh. No, actually my patch DID work. See the line under vpn0 that says
DNS Domain: ~.
So the correct bus call was made and all dns queries SHOULD be directed to the
link-specified listed DNS servers. Your problem actually appears to be that
there are no link-specified dns servers.
See the line
Tim, I have a question for you. When you connect through
network-manager-openconnect-gnome, and type
systemd-resolve --status, what is your link name called? Something like 'tun0'
or 'tap1' or the like?
Because I've been looking around at the openconnect wiki at
Jordi, Sure thing, glad I could help. :)
I wonder if somebody can figure out how to help Tim with
network-manager-openconnect. I tried adding two more conditions for cisco vpn
gre connections but apparently it didn't work or those aren't the kind of links
used. Not sure how to address that
Sorry to here that, I'm frankly not sure what to do about that then :/
At the very least the original patch fixes stuff for openvpn, which is good.
Perhaps someone else could figure out the cisco openconnect thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Anyone using Cisco PPTP/IPsec/openconnect VPN, please test the network
manager with the aforementioned patch or with the updated built .deb
provided here. The updated patch should address more types of VPN links.
Thanks!
** Attachment added: "updated patched .deb packaged network-manager for easy
Tim Shannon, from the comment about network-manager-openconnect-gnome, please
use this updated patch to build the network manager. I added conditions for the
cisco GRE and GRETAP link types, see
https://en.wikipedia.org/wiki/Generic_Routing_Encapsulation and
Yeah, apologies as I'm not sure what link type that openconnect uses /
how to identify an openconnect link. It would be a simple matter to add
a conditional for that in the file I patched, please try that. For now
my patch only addresses openvpn tap or tun links, but I'm sure it could
be expanded
>From the Debian man pages, it seems like this is not in fact a problem
of systemd itself, as it allows for domain routing exclusively for dns
servers on a single interface using the routing-only domain. My patch
effectively just tells the NetworkManager to make a systemd bus call
for the
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
For a Network Manager GUI fix, please see my patch towards the bottom of the
bug report https://bugs.launchpad.net/bugs/1624317
No more DNS leaks through the openvpn network-manager gui! Please let me know
I can confirm this works for multiple vpn connections and after wakeup from
system suspend on Ubuntu 17.04. I encourage you to install the patched .deb or
follow the instructions to build it from source and see for yourself. I'm
honestly so glad this fixes dns leaks for using openvpn through
The actual patch is attached above and can be applied to the source code
which you can build yourself. But for your convenience, I have attached
the .deb file below:
** Attachment added: "patched network manager .deb for easy fix installation on
Ubuntu 17.04"
Please note that this patch and fix only works for Ubuntu 17.04 which relies on
systemd-resolved as a DNS/DNSSEC stub resolver, as well as an LLMNR resolver.
You also need to be using a network-manager plugin like
network-manager-openvpn-gnome.
Install and configure an openvpn connection after
** Patch added: "patch for network-manager source"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4889747/+files/resolved-vpn-dns-leak-fix.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The apps running were firefox, eclipse neon for java developers and a
java application.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sadly, the option block-outside-dns is only supported on Windows
clients. Which is a real shame, because systemd-resolved is leaking DNS
queries everywhere by design. This is a problem with the hardcoded
design of the gnome network manager integrating (or rather...not
integrating) with
Hello all, this bug also prevents me from installing other OS updates.
If anyone can relate to this, then I think security may actually be an
issue if some important security updates cannot subsequently be
installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I am unable to run apport-collect running 4.12-rc3, because I cannot
actually boot my computer (an immediate kernel panic occurs, as
evidenced by adding the output from earlyprintk=efi), so I'm marking
this bug as confirmed. Please also see relevant discussion about this
issue on the Linux Kernel
Public bug reported:
I have an HP Spectre x360 Convertible laptop with an Intel 5500U SoC. In
short, I am completely unable to boot kernel 4.12-rc3, even though I
could boot from 4.12-rc2 perfectly fine. The loading screen does not
appear at all, instead GRUB remains stuck on "Loading initial
It appears a kernel panic is happening immediately while attempting to boot
4.12-rc3, it doesn't happen on 4.12-rc2.
Adding earlyprintk=efi to the grub command line options, I get the following
message (which explains why the bootloader stops at 'loading initial
ramdisk...'):
This was
*** This bug is a duplicate of bug 1693513 ***
https://bugs.launchpad.net/bugs/1693513
Public bug reported:
OS Update stuck in ubuntu software center
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.8.0-53-generic (not installed)
ProcVersionSignature: Ubuntu
Seems this was resolved in 4.12-rc2, mounting ntfs-3g volumes is fine,
doesn't generate a kernel warning! It was fixed in fs/fuse/inode.c at
https://github.com/torvalds/linux/commit/69c8ebf83213e6165b13d94ec599b861467ee2dc
with
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index
This was fixed in 4.12-rc2!
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692143
Title:
fs changes in kernel 4.12 break
Public bug reported:
Fresh install ubuntu but no sound.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm
Okay, so the warning is clearly being generated by the WARN_ON function in
fs/super.c.
I realize I could disable the warning, but that sounds like a bad idea. One
question though,
why would we be verifying if sb->s_bdi is equal to the address of some "struct
backing_dev_info
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879845/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692143
Title:
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879867/+files/version.log
** Also affects: ntfs-3g (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fuse (Ubuntu)
Importance: Undecided
Status: New
--
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879846/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692143
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879847/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692143
Title:
Public bug reported:
Mounting any ntfs partition or ntfs-formatted external drive in kernel
4.12 results in a critical kernel warning. Possible data corruption
could happen, as the drive must be forcibly unmounted. The kernel
warning appears in the syslog literally every single time, this is a
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721
Public bug reported:
I am not sure
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux
*** This bug is a duplicate of bug 1638420 ***
https://bugs.launchpad.net/bugs/1638420
Thank you for sending me your report.
Regards, Nicholas Barnard
From: boun...@canonical.com <boun...@canonical.com> on behalf of Phillip Susi
<ps...@ubuntu.
Thanks for the confirmation Will, glad to see that it works. And yeah I
think this bug should be marked urgent because without the patch, my vpn
connection drops in the same manner every ten minutes or so. The
rationale behind not passing auth-nocache seems pretty clear to me based
on the openvpn
Public bug reported:
I am new to Linux so I do not Know if it was a bug or not
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.14
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic i686
ApportVersion: 2.20.3-0ubuntu8
Architecture: i386
** Summary changed:
- Problem in network-manager-openvpn, openvpn fails during and after downloads.
+ Problem in nm-openvpn-service.c, openvpn connection fails after key
renegotiation because --auth-user-pass is passed with --auth-nocache.
--
You received this bug notification because you are
** Description changed:
So I've been using OpenVPN through the network-manager-openvpn package
integrated into the network manager GUI. I experienced an odd problem
where consistently, during or after downloading (in this case, I tested
by just downloading the kernel tarball from
Okay so I have found the issue pertaining to dns resolution on Ubuntu
16.04.2! There is a critical bug in the package dnsmasq-base here:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776 The fix
hasn't yet been applied to the current version of dnsmasq-base.
This time I have all the
Additional generated built patched package network-manager-openvpn-gnome
** Attachment added: "network-manager-openvpn-gnome_1.1.93-1ubuntu1.1_amd64.deb"
Built patched package.
** Attachment added: "network-manager-openvpn_1.1.93-1ubuntu1.1_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+attachment/4859324/+files/network-manager-openvpn_1.1.93-1ubuntu1.1_amd64.deb
--
You received this bug
Public bug reported:
So I've been using OpenVPN through the network-manager-openvpn package
integrated into the network manager GUI. I experienced an odd problem
where consistently, during or after downloading (in this case, I tested
by just downloading the kernel tarball from kernel.org
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
Okay so I have found the issue pertaining to dns resolution on Ubuntu 16.04.2!
There is a critical bug in the package dnsmasq-base here:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776
The
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677175
Title:
network-manager 1.2.6 won't connect to vpn and displays false
connected message
To manage
Well, scratch that hope and consider me mistaken about Goth Queen's workaround.
It appears that manually setting a fixed DNS server DOES allow for successful
reconnect when the network manager is restarted (whereas before it wouldn't
reconnect period), but just like this bug
Oops, Goth Queen actually provided a solution earlier, it was just difficult
for me to understand at the time. Enter whatever fixed DNS server you want and
set 'Automatic (DHCP) addresses only' under IPv4 Settings in network-manager
for the default network connection. So just manually entering
Okay so since resolvconf and dmasq are not cooperating, I have resorted to
using dnscrypt-proxy. Credit to QkiZ, the dnscrypt-proxy service works EVERY
TIME and ignores the (completely broken) DNS resolution of dnsmasq and
resolvconf. Even with the newest version of network-manager (1.2.6) on
Credit to QkiZ, the dnscrypt-proxy service works EVERY TIME and ignores the
(completely broken) DNS resolution of dnsmasq and resolvconf. Even with the
newest version of network-manager (1.2.6) on 16.04 LTS and all its dependencies:
network-manager
libnm-glib-vpn1
libnm-glib4
libnm0
libnm-util2
I have downgraded both the network-manager and resolvconf package but I still
experience complete DNS resolution failure randomly, where restarting the
network manager has no effect and I cannot connect to the internet. The only
way to get DNS working again is to completely reboot the computer,
Public bug reported:
I tried to install pip by typing in the terminal "sudo apt-get install
python-pip"
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-pip 8.1.1-2ubuntu0.4
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1677175/+attachment/4850128/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
I have been having a rather serious and incredibly annoying problem on the
updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to
manually connect to my VPN provider using openvpn through
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1677175/+attachment/4850129/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677175
Public bug reported:
I have been having a rather serious and incredibly annoying problem on the
updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to
manually connect to my VPN provider using openvpn through the network manager
fails literally any time except bootup. Every
I tried to do an apport and it seg-faulted in the middle of it. However
a few days of researching and looking at the chipset datasheet specific
to my model and I found something useful.
The dmesg report complains about vendor request 0x07 which is a multiple
byte read in the specs, while the
Reporting in from 16.04LTS, this bug still exists and Bug #1388416
appears to be describing the same bug and is marked Confirmed. I just
signed up to post this so I'm still unfamiliar with the platform to find
a way to link to it here.
I have the same issue, though it appeared to change behaviors
Public bug reported:
Juju is now releasing as a snap as the primary means of consumption. For
those still needing a debian package the juju ppas will be maintained.
However from a distro perspective, folks wanting juju should snap
install juju rather than apt install juju. With that in mind, we
Public bug reported:
This file:
/etc/X11/Xsession.d/60x11-common_xdg_path
contains references to $DESKTOP_SESSION variable.
On one of my Ubuntu installs this variable contains: "plasma",
on the other it contains: "/usr/share/xsessions/plasma".
I don't know where either example comes from, but
Still affects Ubuntu 16.04.2 LTS.
I found that going to each server and hitting scroll lock seemed to
magically un-block the hung "/bin/sh /bin/setupcon --force --save"
process and allow the apt upgrade to continue successfully. My setup may
have triggered this bug because I use a KVM for my
The packages for X and Y need to retain this behavior. However, the
zesty archive won't have juju-core or juju-1.25.
** Project changed: juju-reports => juju-release-tools
** Changed in: juju-release-tools
Importance: High => Medium
--
You received this bug notification because you are a
** Also affects: juju-reports
Importance: Undecided
Status: New
** Changed in: juju-reports
Status: New => Triaged
** Changed in: juju-reports
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
401 - 500 of 2587 matches
Mail list logo
