Oh, so I just realized that this option _is_ available on Quantal. So,
it doesn't make sense to backport it to Precise, but it might make sense
to make it available on Quantal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, you should actually be able to remove it completely since Maarten
Lankhorst checked in a commit to define it if it's not found:
(7ce6a2dfd434d8c61d5bd1525a555c19706ac5a2).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Basically the indicator isn't being smart in a multiarch fashion here.
But which package is the indicator in?
indicator-applet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318321
Title:
the
Public bug reported:
The nvidia-settings package has a significant problem with the copyright file.
It is either significantly out of date or plain wrong, neglecting a variety of
files that have different licenses from the main binary. This is most
significant in the portion of the package
Hi Hans,
Yes, this would fix the issue (provided that the copyright file gets
updated with the version from upstream). We (wine staging tree) would
greatly prefer that this package get merged with upstream since upstream
has the lib provided dynamically. Is there a time-table on this
happening
Wow, thanks Alberto - that would be great! We (wine-staging) would like
to link to libXNVCtrl and having it be a dynamic library removes the
ambiguity about what we're supposed to do license-wise (and it
dramatically simplifies our configure check!).
--
You received this bug notification
I am running into the same problem with the nVidia Vulkan driver
(https://launchpad.net/~canonical-x/+archive/ubuntu/vulkan). At first I
thought it was that I updated to 355.00.29, but downgrading to 355.00.26
and it did not fix the issue. This problem was not happening the other
day, but
I am trying to apply this fix for someone and, after some fighting
getting everything setup, I was able to get everything installed to
/usr/local and manually run the custom version. However, it appears
that I still cannot use the Displays panel of unity-control-center to
actually configure the
Public bug reported:
The python3-pyside package (or a relative) should install shiboken.so to
/usr/lib/python3/dist-packages/PySide.
This problem was likely introduced by a bug in the upstream cmake rule,
since this is exactly the problem described and fixed by PYSIDE-55 (
Nevermind, this ended up being that I needed to set the LD_LIBRARY_PATH
to /usr/local/lib when launching unity-control-center. I'm having other
weird problems with this self-compiled version, but I doubt it has
anything to do with this patch.
--
You received this bug notification because you
Is there any chance that the fix can get packaged? Asking users to
install the update through pip is not a very good solution to this
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573689
deb-aelwyn gets the credit for this one, I'm just the monkey entering
info into the bug report ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665565
Title:
python-paramiko 1.16.0-1 incompatible
I pushed a backport of the Yakkety package (3.1.0) to a PPA:
https://launchpad.net/~sweptlaser/+archive/ubuntu/pyopengl
(this worked for me, it's possible that a newer version is needed for
other applications)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The package was not dropped from Ubuntu, it just doesn't work (removing
the package from the repo would be better than having a completely
broken package). I have access to a large number of armhf systems, so
it's possible that I can help upstream get their issue sorted out.
--
You received
I made a PPA for this fix (
https://launchpad.net/~sweptlaser/+archive/ubuntu/pyfftw/+packages ),
but it would be really nice if this could be incorporated into the
official package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We applied this patch to get up and running again:
https://github.com/paramiko/paramiko/pull/714/commits/4752287a7379da61245087ee7e35635a4e42bb3f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665565
Can we get this fixed in 16.04? It is really inconvenient to require
end-users to install pip and build pyfftw themselves...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588863
Title:
importing
@eliasson Wow, if we could finally get this fixed then that would be
really great. Most wine users have both the i386 and x86-64 package
installed (since this is how we provide support for both 32-bit and
64-bit apps on the same system), so this problem affects a lot of users.
--
You received
I tried to apply this on bzr HEAD and got error, going back through the log it
looks like they have a fix for this now (not released for 16.04). It
references another bug that appears to be a duplicate of this issue:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1597537
--
@brian-murray I'm really happy to see that there's finally a fix for
this, is it targeted for a SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597537
Title:
"the cache has no package" error
@pander I do not know who is in charge of this package, but since the
3.1.0 package was available for a Yakkety that made it easy for me to
download the source package and request the build farm to make a version
for Xenial. It looks like they're still packaging 3.1.0 for Zesty, so
if this is a
@cjwatson, I've been getting my work into the habit of deploying Debian
packages for all organization-wide system configuration files. So, when I
noticed the other day that openssh-client 7.3p1+ now supports include
directives I put together a new package that gives all of our internal users
Public bug reported:
It is not currently possible to deploy packages with system-specific SSH
configuration settings without modifying the ssh_config file. Ideally the
default ssh_config file would simply contain:
Include /etc/ssh/ssh_config.d/*
as this would allow packages to deploy such
I am having a similar problem, but I have some additional tidbits:
1) I had the same issue after upgrading from 17.10 to 18.04, but before
rebooting
2) I have the same problem if I downgrade all the strongswan/charon packages to
5.5.1-4ubuntu2.2
3) First connection attempt after reboot does not
So, I've noticed something else that may be relevant. My work's configuration
actually has two DNS servers, which show up like so:
installing DNS server 10.10.0.8 via resolvconf
installing DNS server 10.10.0.2 via resolvconf
However, I saw that there was some probability that it failed after
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
Yes, this is definitely another symptom (duplicate) of bug 1752411 . The
folks on that bug might be people who will know if dig can be used
instead.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
** This bug has been marked a duplicate of bug 1752411
bind9-host, avahi-daemon-check-dns.sh hang forever causes network
connections to get stuck
--
You received this bug notification because you are
** Also affects: strongswan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
bind9-host, avahi-daemon-check-dns.sh hang forever
Definitely a duplicate. @paelzer was suggesting in bug 1786261 that dig
be used instead, do you guys know if that's a reasonable possibility?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411
I think I may have somewhat figured it out. @fermulator, could you get
it to lockup and then run "sudo killall host" in another terminal
window?
It looks like this is some sort of integration issue between the latest
bind9-host (used by avahi-daemon) and the latest systemd, downgrading
either one
I've been trying to figure out how to test this with dig instead, and I think I
found something. If you have a normal /etc/resolv.conf then you see this:
===
$ dig -t soa local.; echo $?
; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> -t soa local.
;; global options: +cmd
;; Got answer:
;; WARNING:
@paelzer, it is making an usual call to host and checking the return:
LC_ALL=C host -t soa local. 2>&1
and theoretically this maps to:
LC_ALL=C dig -t soa local. 2>&1
Practically, I don't think this works. I do not have a "local." start
of authority record and when I run these commands I get a 1
How are your LVM2 volumes configured? Based on that segfault, I would
guess that it has something to do with that (and would not necessarily
be reproducible if the volume configuration is not similar).
I would have a hard time believing that it has anything to do with our
custom Debian packages.
@dhookersl I believe that if he ran apt-clone on your file that it would
have installed our custom packages for him, so his environment should be
perfectly identical to yours except for the charon config file (that is
the only config file we don't package).
--
You received this bug notification
@kleber-souza I don't think that I have anything running trusty that I
can test with, but I can easily test on xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759920
Title:
** Summary changed:
- intel-microcode 3.20180312.0 causes lockup at login screen(w/
linux-image-4.13.0-37-generic)
+ intel-microcode 3.20180312.0 causes lockup at login screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- intel-microcode 3.20180312.0 causes locks up at login screen(w/
linux-image-4.13.0-37-generic)
+ intel-microcode 3.20180312.0 causes lockup at login screen(w/
linux-image-4.13.0-37-generic)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I've identified a couple more systems that are affected by this issue:
iucode-tool: system has processor(s) with signature 0x00040651
iucode-tool: system has processor(s) with signature 0x000806e9
That second one was actually having trouble with 4.4.0-116-generic
(boots fine with
That's very interesting John, that could also explain why we had a system:
1) get updated
2) fail on 4.4.0-116-generic
3) work on 4.4.0-112-generic
4) install 4.13.0-36-generic and 4.13.0-37-generic
5) fail on 4.13.0-36-generic and 4.13.0-37-generic
6) get intel-microcode downgraded to
By any chance, do all of you have sssd installed? One of my colleagues
(Kyle Etsler) has established a relationship between this problem and
having that package installed. I've verified this on my own machine
now, and it makes some sense given that sssd is involved in the login
process.
--
You
** Attachment added: "cpuinfo for an affected system"
https://bugs.launchpad.net/linux/+bug/1759920/+attachment/5095246/+files/cpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759920
Public bug reported:
I don't know if this is a problem with the kernel or the microcode, but
we have a significant number of computers in our organization (on both
16.04 and 17.10) that fail if they have both updated. Booting with
either linux-image-4.13.0-36-generic or intel-microcode
** Project changed: linux => 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/1759920
Title:
linux-image-4.13.0-37-generic locks up at login screen with intel-
microcode 3.20180312.0
> Does the lockup happen as soon as you reach the login screen or does
it happen once you put in your password and hit enter?
It sometimes happens as soon as the login screen shows up, sometimes it
happens after you hit enter, and roughly 1:8 tries it will make it all
the way to the desktop.
>
44 matches
Mail list logo
