** Changed in: firefox (Ubuntu)
Status: New => 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/1936647
Title:
right-click popups transparent after upgrade to Firefox 90
To manage
Issue no longer present in 90.0.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936647
Title:
right-click popups transparent after upgrade to Firefox 90
To manage notifications about this bug go
** Bug watch added: Debian Bug tracker #991776
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991776
** Also affects: virt-viewer (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991776
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
Public bug reported:
Upon upgrade to Firefox 90, right-click popups appear transparent.
I am using the Blackbird gtk theme. If I switch to Adwaita-dark, the problem
goes away.
I encountered this issue on another system with the direct download from
Mozilla, so this is likely an upstream issue, b
Ryan,
Thank you so much for taking the time to go over the constraints and
competing goals. It's always helpful to know what constituencies are
involved.
> That said, I do think that cloud-init can make it easier to enable ipv6 where
> it's desired (but without having to write your own network co
> If you are not providing any network config to cloud-init, current the
default fallback is to DHCP (ipv4) only
This is precisely the bug I am reporting.
> And for ipv6 config, I suspect you'll want to provide an netplan
config with:
In the year 2020, IPv6 should be a first class citizen and I
Executive summary: I expected this test to go much differently. This bug
should probably be "cloud-init does not wait for IPv6 config in dual-
stack network"
--
One of my initial tests was in my primary dual-stack network, and it
also worked similar to your example.
Excerpt from my deploy script
Public bug reported:
In ubuntu-20.04-server-cloudimg-amd64-disk-kvm.img provided on cloud-
images.ubuntu.com does not have IPv6 enabled by default. This precludes
the use of an IPv6 webserver (URL supplied with the SMBIOS option) to
feed the NoCloudNet datasource.
I can enable IPv6 using "network
Public bug reported:
May 13 02:20:25 cloudtest snapd[780]: stateengine.go:150: state ensure error:
persistent network error: Get https://api.snapcraft.io/api/v1/snaps/sections:
dial tcp 91.189.92.19:443: connect: network is unreachable
May 13 02:20:25 cloudtest systemd[1]: Finished Wait until sn
*** This bug is a duplicate of bug 1731502 ***
https://bugs.launchpad.net/bugs/1731502
There was just an update to the samba package, and apparently it turns
the nmbd service back on. Had to ssh in and disable it to manually apply
the update after failing with Ansible.
--
You received this b
Public bug reported:
If the display on the libvirt server is an IPv6 address (::1) instead of
an IPv4 address (127.0.0.1), the client cannot connect when socat is
installed on the libvirt server.
>From the client:
--
kjotte@daedalus:~$ virt-viewer -v -c qemu+ssh://agamemnon.home.nivex.net/system
I just ran 2to3 on obamenu and it looks like a simple fix. Maybe we can
push this upstream to Debian and not need the python2 call?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816473
Title:
obame
** Patch added: "Fixup obamenu for python3"
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1816473/+attachment/5334079/+files/obamenu-py3.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
When installing the samba package:
invoke-rc.d: initscript nmbd, action "start" failed.
● nmbd.service - Samba NMB Daemon
Loaded: loaded (/lib/systemd/system/nmbd.service; disabled; vendor preset:
enabled)
Active: failed (Result: timeout) since Sat 2020-02-22 18:47:14
IPv6 should not be completely disabled on any system. This is not in
keeping with Best Current Practices. See RFC 6540 (BCP 177). If an admin
has manually disabled IPv6 on their system, it is their responsibility
to also disable any services listening on IPv6 by default. This "fix" is
antithetical
I would not trust ecryptfs anymore.
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840
Use the time to migrate your data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title
Public bug reported:
/usr/bin/obamenu in the openbox package requires Python 2, but the
openbox package has no dependency on a python2 package. This causes an
error dialog to pop up when selecting the Applications menu.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openbox 3.6.1-7ubuntu0.
At some point along the line this bug has been fixed:
kjotte@mystic:/tmp/sane-backends-1.0.27/backend$ grep -n gethostbyname pixma*
kjotte@mystic:/tmp/sane-backends-1.0.27/backend$ grep -n getaddrinfo pixma*
pixma_bjnp.c:849: if (getaddrinfo(host , service, NULL, &results) == 0)
pixma_bjnp.c
I no longer receive the "Network is unreachable" message from the
command-line tool, so that part is fixed.
I was unable to test the complete workflow of reporting a bug because
login.launchpad.net does not have records therefore the browser
window that was opened died in its tracks. I realiz
Public bug reported:
virt information is no longer being reported after the upgrade to 18.04
(collectd 5.7.2-2ubuntu1).
Logs are filled with:
Dec 3 15:25:17 athens collectd[1548]: virt plugin: Array index out of bounds:
tag_index = 9
The issue has been reported upstream:
https://github.com/col
Public bug reported:
kjotte@daedalus:~$ cryptmount lukstest
Enter password for target "lukstest":
Failed to extract LUKS key for "lukstest" (errno=95)
Failed to extract cipher key
This issue has been fixed upstream:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888444
Please consider backpo
Public bug reported:
Attempted to mount my ecryptfs Private folder for the first time after
upgrading from 16.04 -> 18.04.
$ ecryptfs-mount-private
Enter your wrapping passphrase:
Inserted auth tok with sig [redacted] into the user session keyring
mount: No such file or directory
Workaround:
$ s
Public bug reported:
Had to dpkg --force-depends --remove libgnuradio-iqbalance0 in order to
get the 16.04 -> 18.04 upgrade to complete.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gr-iqbal 0.37.2-11
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-ge
Possibly related upstream bug:
https://bugzilla.xfce.org/show_bug.cgi?id=12975
** Bug watch added: Xfce Bugzilla #12975
https://bugzilla.xfce.org/show_bug.cgi?id=12975
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
chrony will still start even if the network isn't up. It will just not
report any reachability to peers (or possibly any peers at all). For
some reason chrony was straight up not running. Not sure why that was
the case.
My guess is the high CPU from the chronyc command invoked by the nm-
dispatche
icarus is my virtual desktop to test all manner of things. It is so
named for if I fly it too close to the sun I just rebuild it. As such, I
did just that, and was unable to reproduce this issue.
** Changed in: chrony (Ubuntu)
Status: New => Invalid
--
You received this bug notification b
Public bug reported:
On a fresh install of Xubuntu 18.04, xfce4-battery-plugin is using is
using most of a CPU, is currently the top memory consumer on the
machine, and is driving the temperature up. Killing the process causes
it to restart, and this behavior returns within a day or so.
This appe
ptp_kvm is being loaded in /etc/modules on my machine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779966
Title:
chrony fails to start, nm-dispatcher hook causes high CPU load
To manage notificat
The information I provided is taken from a VM upon logging in after
initial boot. I provided my chrony.conf as attachment precisely to head
off the question about custom config.
The logs were not clear on why chrony is not starting cleanly.
Regardless, attempts to call chronyc by the NM dispatcher
** Attachment added: "chrony.conf"
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779966/+attachment/5159357/+files/chrony.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779966
Title:
Jul 3 19:44:07 icarus systemd[1]: chrony.service: Start operation timed out.
Terminating.
Jul 3 19:44:07 icarus systemd[1]: chrony.service: Failed with result 'timeout'.
Jul 3 19:44:07 icarus systemd[1]: Failed to start chrony, an NTP client/server.
--
You received this bug notification becau
Public bug reported:
Chrony is failing to start correctly, and the chronyc command launched
by the NetworkManager dispatcher hook is going to 100% CPU.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chrony 3.2-4ubuntu4.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linu
Is there any chance the new libtirpc will get backported into 18.04.1?
Not having IPv6-enabled autofs is going to wreck a lot of my workflow
once I start upgrading machines in August. I'm currently running a
custom build of autofs with libtirpc in 16.04 to enable this
functionality.
--
You receiv
At some point this started working right again. *shrug*
** Changed in: xfce4-cpufreq-plugin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744145
Title:
freq
I'm afraid I cannot. I am no longer in possession of the hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682921
Title:
sluggish system, kernel errors on Inspiron 1525
To manage notificatio
I've gotten no motion upstream (Debian) on this. Is this something
Ubuntu can pick up for its installer?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641656
Title:
initramfs parameters invalid for
I tested mainline ( http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.15-rc9/linux-
image-4.15.0-041500rc9-generic_4.15.0-041500rc9.201801212130_amd64.deb )
as I have been asked to do on other kernel issues. The problem persists.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux-hwe
I have tested the package provided by ahasenack in ppa:autofs-ipv6-1101779
A 'cd' into the autofs managed directory worked perfectly right off the bat.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/110
Problem still present in newly issued 4.13.0-31-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743495
Title:
system stutters heavily with usb3 ExpressCard inserted
To manage notifications a
Public bug reported:
After upgrading to linux-image-4.13.0-26-generic from 4.10.0-42-generic,
the frequency displayed in the CPU Frequency Monitor applet has been a
constant 3.20GHz. I have verified that the CPU governor is working
correctly with cpufreq-info at the command line.
ProblemType: Bug
lspci output of device from 4.10
** Attachment added: "lspci-usb3.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1743495/+attachment/5037646/+files/lspci-usb3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Attaching dmesg output from booting 4.13 with the card inserted. Some
xhci messages may be of interest.
** Attachment added: "dmesg-x220-usb3-20180115.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1743495/+attachment/5037644/+files/dmesg-x220-usb3-20180115.txt
--
You received
Public bug reported:
I have a USB3 ExpressCard adapter I use with my ThinkPad X220. It was
mostly working under 4.10.0-42-generic, but once I got the
4.13.0-26-generic update my system now stutters to the point that it is
almost unusable until the card is ejected.
By "mostly working" I mean that
I am indeed still having this issue with latest mainline. (
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc8/linux-
image-4.15.0-041500rc8-generic_4.15.0-041500rc8.201801142030_amd64.deb )
You'll forgive me if I am not interested in filing this issue upstream. As an
end user, my time is so
I just tested this with targetcli-fb in 17.10 and it gleefully allowed
me to add a portal for an address that isn't even on the system, but I
do see it listening in "ss -a -6" output. I guess this at least avoids
the problem of upgrading my server from 16.04 -> 18.04 when the time
comes. Sadly it l
I just tested this with targetcli-fb in 17.10 and it gleefully allowed
me to add a portal for an address that isn't even on the system, but I
do see it listening in "ss -a -6" output. I guess this at least avoids
the problem of upgrading my server from 16.04 -> 18.04 when the time
comes. Sadly it l
There is a patch filed against Debian 737679 that fixes the problem. If
it doesn't make it through Debian in time, can Ubuntu pick up this patch
for the next LTS? It would be a shame for another two years to go by and
not have proper IPv6 support.
--
You received this bug notification because you
** Attachment added: "Kernel trace from mainline"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731784/+attachment/5037419/+files/polaris-trace-20180115.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
root@polaris:/tmp# wget
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/linux-image-4.14.0-041400-generic_4.14.0-041400.201711122031_amd64.deb
--2018-01-15 12:11:59--
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/linux-image-4.14.0-041400-generic_4.14.0-041400.201711122031_amd64.deb
Re
Oof, it seems to have cut where it says cut here. Attaching latest
trace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731784
Title:
system slow to start, kernel trace on Inspiron 1525
To manage
I just lost a good chunk of my evening to this. I'm using native IPv6
from my upstream ISP and therefore do not have control of rDNS. I was
expecting the documented behavior and didn't realize I'd hit a bug until
on a lark I added the IP address of the NFS server to the client's
/etc/hosts file.
-
** Bug watch added: Debian Bug tracker #883126
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883126
** Also affects: darkice via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883126
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Still a problem two years later:
$ lsb_release -d
Description:Ubuntu 17.10
$ darkice -c ./darkice.cfg
DarkIce 1.3 live audio streamer, http://code.google.com/p/darkice/
Copyright (c) 2000-2007, Tyrell Hungary, http://tyrell.hu/
Copyright (c) 2008-2013, Akos Maroy and Rafael Diniz
This is free
This has been going on for awhile. Related bug #1682921
The last time it worked right (if memory serves) was the LTS kernel that
shipped with 16.04.
I will test mainline as time permits.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The system is slow to start / log in.
[ 65.504191] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]]
*ERROR* [CRTC:35:pipe B] flip_done timed out
[ 65.608196] vblank wait timed out on crtc 1
[ 65.608270] [ cut here ]
[ 65.608310] WA
There has been no activity on this bug in nearly a year. We're a week
away from releasing 17.10, which will put us well on the way to being in
the dev cycle for the next LTS. I have grave concerns about a fix making
it into the repo in time having witnessed deadlines come and go on
previous release
In addition to the already linked bug, Debian bug 737679 also appears to
be closely related: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=737679
** Bug watch added: Debian Bug tracker #737679
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737679
--
You received this bug notification
Public bug reported:
A startup script is being patched to load module-x11-bell with a given
sample name:
debian/patches/0006-load-module-x11-bell.patch:+@PACTL_BINARY@ load-
module module-x11-bell "display=$DISPLAY" "sample=bell.ogg" > /dev/null
yet in the default example:
src/daemon/default
Upstream doesn't care. Closing this out to clean up my bug list.
** Changed in: xastir (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/454740
Title:
xastir
Last activity was three years ago and the other affected suites indicate
Fix Released. Closing this out to tidy up my bug list.
** Changed in: ubuntustudio
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Clearing out my bug list
** Changed in: krb5-auth-dialog (Ubuntu)
Status: New => 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/1421052
Title:
krb5-auth-dialog does not accept in
This appears to have been an errant config setting. The port is
configurable in the Audio Options panel.
** Changed in: gqrx-sdr (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
kjotte@polaris:/tmp$ wget
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7/linux-image-4.11.0-041100rc7-generic_4.11.0-041100rc7.201704161731_amd64.deb
--2017-04-18 14:17:58--
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7/linux-image-4.11.0-041100rc7-generic_4.11.0-041100rc7.201
And just to be thorough I tested with the intel-microcode package
removed. No change in behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682921
Title:
sluggish system, kernel errors on Inspi
Public bug reported:
Process in question:
6832 ?Rl 2430:25 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libbattery.so 18 14680129 battery
Battery Monitor Show and monitor the battery status
htop lists its RSS as 404M (20% of the memo
Public bug reported:
Starting in 16.10, this machine started taking forever to boot.
Occasionally hangs for a few to tens of seconds. Under 17.04, dmesg is
flooding with similar messages:
[57593.526006] [ cut here ]
[57593.526083] WARNING: CPU: 1 PID: 994 at
/build/linux-
Is there anything else you need from me to be able to merge this patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610479
Title:
interface-order needs definitions for systemd predictable names
** Bug watch added: Debian Bug tracker #853994
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853994
** Also affects: partman-iscsi (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853994
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
So it looks like this was merged into 16.10 (3:20150815-2ubuntu3 vs
3:20121221-4ubuntu1.1 per packages.ubuntu.com). Should this be closed
out as Fix Released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Thank you for the swift and thorough reply. It is appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656054
Title:
Unable to validate GoDaddy signed certs
To manage notifications about thi
kjotte@daedalus:~$ openssl s_client -CApath /etc/ssl/certs -connect
api-v1.weather.gov:443
CONNECTED(0003)
depth=0 OU = Domain Control Validated, CN = nws.noaa.gov
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 OU = Domain Control Validated, CN = nws.noaa.go
Public bug reported:
I am updating a script to use a new version of the US National Weather
Service API and am running into a certificate problem.
kjotte@daedalus:/tmp$ curl https://api-v1.weather.gov/
curl: (60) server certificate verification failed. CAfile:
/etc/ssl/certs/ca-certificates.crt
FWIW, changing that partition to an rpartition will at least get things
online.
** Patch added: "config_live.patch"
https://bugs.launchpad.net/ubuntu/+source/rtslib/+bug/1643069/+attachment/4779605/+files/config_live.patch
--
You received this bug notification because you are a member of Ubu
Public bug reported:
The service startup ate the traceback, so I keyed it in by hand:
>>> import rtslib
>>> config = rtslib.Config()
>>> config.load("/etc/target/scsi_target.lio", allow_new_attrs=True)
>>> list(config.apply())
No handlers could be found for logger "Config"
Traceback (most recent c
This may need to be filed against the vlan package as
/etc/network/if-pre-up.d/vlan is owned by same.
It was my understanding, however, that vconfig was deprecated in favor of 'ip
link' as used in my workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
root@atlantis:/etc# ifup enp2s0.121
Cannot find device "enp2s0.121"
Failed to bring up enp2s0.121.
Workaround:
Add
pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121
to /etc/network/interfaces declaration.
** Affects: ifupdown (Ubuntu)
Importance:
** Patch added: "iscsi_settings.patch"
https://bugs.launchpad.net/ubuntu/+source/partman-iscsi/+bug/1641656/+attachment/4778463/+files/iscsi_settings.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
When an iSCSI offload card is in use, in my case a QLE4060C (qla4xxx
driver), partman-scsi blindly assumes that because the root device is on
an iSCSI volume it is using the installer selected network device.
I'm having trouble following the logic in init.d/iscsi, but I think
Public bug reported:
In init.d/iscsi the portal address is collected thusly:
echo "$(cat "$connectiondev/persistent_address"):$(cat
"$connectiondev/persistent_port"),$(cat "/sys/$sessiondev/tpgt")" >iscsi_portal
resulting in an iscsi_portal file looking like
2606:a000:a449:5900::4:3260,1
In fin
I found the problem in the installer and have filed a separate bug
against it. This turned out to be a lousy bug report, but hopefully my
flailing can save someone some pain down the road.
** Changed in: open-iscsi (Ubuntu)
Status: New => Invalid
--
You received this bug notification bec
https://bugs.launchpad.net/debian/+source/ifupdown/+bug/1629972 appears
related to the shutdown side of things, though I'm not doing anything
cloud-y at the moment. Comment 4 in that bug seems to indicate that
doing iSCSI on the main interface, or at least one configured
dynamically, is frought wit
Finally found the startup problem:
$ cat /tmp/iscsi.initramfs
ISCSI_TARGET_NAME="iqn.2016-11.net.nivex:storage.istest"
ISCSI_TARGET_IP="2606"
ISCSI_TARGET_PORT="a000:a449:5900::4:3260"
ISCSI_TARGET_GROUP="1"
ISCSI_USERNAME="istest"
ISCSI_PASSWORD="123456789012"
Whatever is generating the initram
So it turns out this is a bit of a "perfect storm" involving an IPv6-only
interface.
I've filed a bug upstream at: https://github.com/Datera/rtslib/issues/17
** Summary changed:
- unable to add VLAN interface address as iscsi portal
+ unable to add IPv6-only interface address as iscsi portal
**
Ah, this appears to be a fault in rtslib not enumerating the VLAN
interface:
>>> import rtslib.utils
>>> rtslib.utils.list_eth_names()
['lo', 'eth0']
** Package changed: targetcli (Ubuntu) => rtslib (Ubuntu)
** Summary changed:
- unable to add ULA address as iscsi portal
+ unable to add VLAN i
Public bug reported:
When I attempt to add a ULA address as a portal IP:
/iscsi/iqn.20.../tpg1/portals> pwd
/iscsi/iqn.2000-12.net.nivex:storage.omashu/tpg1/portals
/iscsi/iqn.20.../tpg1/portals> create fd60:e0:a0f4:121::4
Using default IP port 3260
IP address does not exist: fd60:e0:a0f4:121::4
Might as well. When upstream says "Well no one else is complaining"
you're not likely to get anywhere. Just because CPUs have gotten faster
doesn't mean the problem has gone away, only masked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
For this system, a pure network boot was not practical, so USB storage
for the EFI System Partition and /boot are used.
Steps to reproduce:
- Use Ubuntu Server installer to log in to iSCSI target
- Install ESP and /boot on local USB (sda1,2)
- Install swap and /on resulting b
There was a response to the upstream bug indicating the method I used in
my patch would be insufficient. I don't have the skill to whip it into
shape to get it accepted, sadly. If someone who is a developer could
look at the bug in the GNOME bugtracker and rework the patch a bit they
will probably
Can confirm this still affects 16.04 LTS (autofs 5.1.1-1ubuntu3)
attempting to mount entry /net/data6
lookup_mount: lookup(file): looking up data6
lookup_mount: lookup(file): data6 -> atlantis.home.nivex.net:/data
parse_mount: parse(sun): expanded entry: atlantis.home.nivex.net:/data
parse_mount:
Public bug reported:
Documentation at http://gqrx.dk/doc/streaming-audio-over-udp
shows data should be sent to UDP port 7355.
tshark -p -i lo udp
shows the data is going to UDP port 16 instead.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gqrx-sdr 2.5.1-1
ProcVersionSignature: Ubuntu 4.
I'm curious why this has been given such an abysmally low priority
(wishlist) when a similar bug (#1094345) was fixed quickly a few years
ago and a patch has been submitted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Previous patch did not fully account for PCI bus description. New patch
attached.
** Patch removed: "interface-order.patch"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+attachment/4727594/+files/interface-order.patch
** Patch added: "interface-order.patch"
https://bu
Pattern matching and I have never been fast friends, but this appears to
work in my one little test case.
** Patch added: "interface-order.patch"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+attachment/4727594/+files/interface-order.patch
--
You received this bug notifi
** Bug watch added: Debian Bug tracker #834928
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834928
** Also affects: dhcp via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834928
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a mem
Public bug reported:
Another release, another round of interface name changes.
This time systemd has gotten into the fray to make things even more
interesting.
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
As such, IPv4 resolvers are now being preferred ove
This is still an issue in Ubuntu Server 16.04.1. I have the following in
my /etc/network/interfaces file:
# The primary network interface
auto ens3
iface ens3 inet dhcp
# This is an autoconfigured IPv6 interface
iface ens3 inet6 auto
dhcp 1
And on startup:
Aug 5 15:55:23 flounder dhclient[24
Apologies for the delay in getting the test done.
Test procedure:
- Enable proposed per instructions
- Update packages
# apt-get -t wily-proposed install libvirt-bin
...
Setting up libvirt0 (1.2.16-2ubuntu11.15.10.1) ...
Setting up libvirt-bin (1.2.16-2ubuntu11.15.10.1) ...
...
- Reload apparmor p
Going back through old bug reports and stumbled across this still open.
Fired up xastir on my ham box to check it out.
Machine I'm running it on is significantly newer, but I am indeed still
seeing about an 8% CPU load from the xastir 2.0.6 process on Ubuntu
15.10. I strace'd the running process a
utopic no longer under support and subsequent versions of the package
are fixed. This bug can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421052
Title:
krb5-auth-dialog does not accept
Public bug reported:
kjotte@pegasus:~$ grep ^server darkice.cfg
server = marconi.home.nivex.net
kjotte@pegasus:~$ host marconi.home.nivex.net
marconi.home.nivex.net has IPv6 address 2606:a000:a461:4500:5054:ff:febc:58a2
kjotte@pegasus:~$ darkice -c darkice.cfg
DarkIce 1.2 live audio streamer, ht
1 - 100 of 239 matches
Mail list logo
