** Tags added: sts
** Also affects: sudo (Ubuntu Jammy)
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/2104840
Title:
sudo_logsrvd TLS log transport in Ja
Public bug reported:
[ Impact ]
Users of sudo_logsrvd in Jammy are unable to configure TLS transport as
sudo was built without OpenSSL in Jammy.
This functionality is available in Noble and above as OpenSSL was inadvertantly
included in sudo builds: 564d6d7f in cyrus-sasl2 introduced an indirec
Hi, just checking in on the status of this since LP#2093164 is waiting
on it. Is this still blocked?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using
A reminder that the snap is disabled would be ideal, but "not found" is
also appropriate here IMO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104201
Title:
LXD installer attempts to install when
Looks good to me, thanks for hopping on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104201
Title:
LXD installer attempts to install when LXD snap is installed &
disabled
To manage notifi
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104201
Title:
LXD installer attempts to install when LXD snap is installed &
disabled
To manage notifications about this bug go t
I ran into this with autopkgtest (man 1 autopkgtest-virt-lxd), so it
hung for a while and then failed as the first lxc command it ran didn't
do anything.
I haven't looked at the code but an early return (with some kind of
descriptive error message) when LXD is disabled would be great. :)
--
You
Public bug reported:
Install and disable LXD in Ubuntu 24.04
```
sudo snap install lxd
sudo snap disable lxd
```
Then run a command with lxc:
```
$ lxc ls
Installing LXD snap, please be patient.
```
** Affects: lxd-installer (Ubuntu)
Importance: Low
Status: New
--
You received
** Description changed:
+ [ Impact ]
+
+ `netplan try` fails to roll back network changes after an edit to
+ /etc/netplan/50-cloud-init.yaml. This occurs using both networkd and
+ NetworkManager backends.
+
+ A user makes changes to their netplan configuration over ssh, expecting
+ that if the s
** Changed in: netplan.io (Ubuntu Focal)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu Noble)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu Oracular)
Status: New => Confirmed
Opened a PR: https://github.com/canonical/netplan/pull/548
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083029
Title:
Try does not recover network
To manage notifications about this bug go to:
ht
I've done some more looking at this and the bug runs pretty deep. During
`netplan try`, netplan backs up both its configuration in /etc/netplan
and the backend configurations for systemd-networkd and NetworkManager
[1]. The problem with this is that the restored config files aren't
picked up by sys
Looks like the symlink described in 1ecc312721 (/usr/lib/linux-
tools/6.8.0-1023-azure/lib -> /usr/lib/linux-azure-tools-6.8.0-1023/lib)
doesn't exist with package linux-tools-6.8.0-1023-azure, likely because
the link's target doesn't exist. I checked the corresponding links in
linux-realtime-tools
** Tags removed: verification-done-noble-linux
** Tags added: verification-failed-noble-linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089411
Title:
python perf module missing in realtime kern
_64 x86_64 GNU/Linux
wesley@noble3:~$ python3 -c 'import perf; [print(c) for c in perf.cpu_map()]'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/perf/__init__.py", line 26, in
raise KernelNotFoundError()
perf.KernelNo
All set, thanks.
```
wesley@oracular2:~$ uname -a
Linux oracular2 6.11.0-1006-realtime #6-Ubuntu SMP PREEMPT_RT Mon Feb 17
15:51:31 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
wesley@oracular2:~$ python3 -c 'import perf; [print(c) for c in perf.cpu_map()]'
0
```
** Tags removed: verificat
** Tags removed: verification-needed-oracular-linux
** Tags added: verification-failed-oracular-linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089411
Title:
python perf module missing in realt
Hi, I'm still seeing this bug with 6.11.0-1006-realtime, which should
contain the patch [1] (thanks for the help Juerg)
```
wesley@oracular2:~$ uname -a
Linux oracular2 6.11.0-1006-realtime #6-Ubuntu SMP PREEMPT_RT Mon Feb 17
15:51:31 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
wesley@orac
Hi Danilo, thanks for the note. I've updated the description with the
netplan yaml and opened https://github.com/canonical/netplan/pull/539
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095203
Title:
** Description changed:
Hello,
When using physical NIC passthrough in LXD containers [1], netplan fails
when trying to run `udevadm`.
Using these LXD devices for the container, where enp6s0 is a spare physical
NIC:
```
devices:
- eth0:
- name: eth0
- nictype: physical
Public bug reported:
Hello,
When using physical NIC passthrough in LXD containers [1], netplan fails
when trying to run `udevadm`.
Using these LXD devices for the container, where enp6s0 is a spare physical NIC:
```
devices:
eth0:
name: eth0
nictype: physical
parent: enp6s0
typ
Hi friends,
Since Numba 0.59 has been released with support for python 3.12, are
there plans to include numba in noble-updates/universe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052661
Title:
Public bug reported:
Hi,
We're seeing failures of an ext4 resize on LVM and Ceph block devices in
the LXD CI; the following call trace happens during resize2fs of an ext4
FS on an LVM lv. I'll also upload an apport report. Let me know if
there's anything else I can provide!
---
[ 54.268802] E
Hi, gentle ping on this; is there an ETA for this to land in 22.04? Let
me know if I can help with testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597017
Title:
mount rules grant excessive p
@Portia - DT update is required: https://github.com/Xilinx/linux-
xlnx/commit/6472141dd7401ff43fc0fbb3dbc253454c5be2ee
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055237
Title:
Backport ps uart
Thanks for the note Mauricio.
The bug is not present in Jammy.
I've edited the bug description to include a reproducer that reflects
the message length limit.
** Description changed:
POST requests to an apache2 server with the below configuration do not
- forward the message body.
+ forward t
Public bug reported:
POST requests to an apache2 server with the below configuration do not
forward the message body.
Affected versions:
apache2 2.4.41-4ubuntu3.17 in focal
Steps to reproduce:
sudo apt-get install apache2
sudo a2enmod proxy
sudo a2enmod proxy_http
Add /etc/apache2/sites-enable
This also affects ceph-volume 19.2.0~git20240301.4c76c50-0ubuntu6 in
Noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064717
Title:
ceph-volume needs "packaging" module
To manage notifications
** Attachment added: "apport.linux-image-6.5.0-28-generic._9l2i4n1.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064176/+attachment/5772647/+files/apport.linux-image-6.5.0-28-generic._9l2i4n1.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Hi, cross posting this from
https://github.com/canonical/lxd/issues/12161
I've got a lxd cluster running across 3 VMs using the fan bridge. I'm
using a dev revision of LXD based on 6413a948. Creating a container
causes the trace in the attached syslog snippet; this causes the
** Attachment added: "bug.webm"
https://bugs.launchpad.net/ubuntu/+bug/2059848/+attachment/5761449/+files/bug.webm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059848
Title:
Error in the calen
Public bug reported:
The error happens when I click on the last days of the calendar
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
A
Public bug reported:
Installation failed at 1st attempt in Try Ubuntu mode.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.15
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon z
Public bug reported:
We would like to be able to fully install Ubuntu over https. Using our own
certificate authority to secure the apt repo over https. So for example in our
Autoinstall user-data file we would have something like:
apt:
primary:
- arches: [default]
uri
Public bug reported:
The release upgrade from 20.04 to 21.04 kept failing because some
foreign packages were installed. After I attempted removing the said
packages - using the "Software & Updates" GUI tool, the upgrade failed
because "the essential package 'ubuntu-minimal' could not be located on
I am the user with the bug reported here
https://github.com/JuliaLang/julia/issues/40222.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891205
Title:
Julia crashes only on Ubuntu
To manage notifi
The comment #65 was what worked for me.
https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1840725/comments/65
My OS installation is Kubuntu 18.04.
Additional and more detailed info about my laptop:
```
$ uname -a
Linux ioku 5.3.0-59-generic #53~18.04.1-Ubuntu SMP Thu Jun 4 14:58:26 U
Thanks for fixing this @raharper!
How can I make use of this so I can finally successfully run the installation?
Do I just need to select the "Update Installer" option again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Has this bug been confirmed as fixed?
I'm still experiencing this error, even when using the new installer as
prompted during the update.
https://bugs.launchpad.net/subiquity/+bug/1878890
Unless something else is going on in with my installation...?
--
You received this bug notification becaus
Did a modprobe snd-hda-intel and unblacklisted snd_hda_intel, audio
works!! My bad for disturbing, anyway, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864061
Title:
PCI/internal sound car
I didn't have any problems until some hours ago (I believe it started
after updating to kernel -46). Now I'm riding this boat. Nothing helps,
already tried everything, even regression to kernel -40.
Before reinstalling alsa-base, my Audio Driver showed up as
snd_hda_intel, but now it just shows up
*** This bug is a duplicate of bug 1825497 ***
https://bugs.launchpad.net/bugs/1825497
Experiencing the same behavior in chromium. Running "chromium-browser
--no-sandbox" workaround works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
it crashes about 3/4 into install
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.9 [modified: usr/share/ubiquity/apt-setup]
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0u
Public bug reported:
Description:Ubuntu 18.10
Release:18.10
phpmyadmin:
Installed: 4:4.6.6-5
Candidate: 4:4.6.6-5
Version table:
*** 4:4.6.6-5 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu cosm
Public bug reported:
Failed on install
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Fri Jun 15 1
Public bug reported:
Was attempting to install php with the command "apt-get install php".
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: php7.2-common 7.2.5-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion:
Public bug reported:
using the daily bionic beaver build, installing xrdp via apt and adding
a polkit rule for color profile I try to connect. it seems to connect
but i'm seeing random "system program problem" dialogs and when i do
connect the desktop is incomplete. the bar along the left is not
Public bug reported:
Running Ubuntu 17.10
Was attempting to install network-manager-l2tp which depends on xl2tpd
1.3.8+dfsg-1
Logs:
Setting up xl2tpd (1.3.8+dfsg-1) ...
Job for xl2tpd.service failed because a timeout was exceeded.
See "systemctl status xl2tpd.service" and "journalctl -xe" for
Public bug reported:
Fresh install Lubuntu 17.10 desktop i386. Dell Latitude D600. Defaults
on install except having to "forcepae" on boot. "apt --fix-broken
install" gives the following errors -
Reading package lists... Done
Building dependency tree
Reading state information... Done
Co
Public bug reported:
Cannot install Chinese (simplified)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libfreerdp-plugins-standard:amd64
1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_6
I upgraded from 17.04 and installed OpenVPN just fine. But then I did a
clean install and now I'm getting the same bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725525
Title:
Cannot complete i
Public bug reported:
pass
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.18-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-80.101-generic 4.4.70
Uname: Linux 4.4.0-80-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun Jun 18 19:49:11
Public bug reported:
I use this python and i install on hands
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: python3.5-minimal 3.5.3-1
ProcVersionSignature: Ubuntu 4.8.0-47.50-generic 4.8.17
Uname: Linux 4.8.0-47-generic i686
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
Date: Sa
** Merge proposal unlinked:
https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+merge/321029
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575779
Title:
hostnamectl
** Merge proposal unlinked:
https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+merge/321029
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575779
Title:
hostnamectl
@Wolf Unfortunately for me even after fully clearing the device list on
my Bose QC35s it still will not pair. It immediately fails when I
attempt to pair.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
@Konrad @Jim The headphones pair flawlessly with every device I have in
my house including my laptop on the windows partition. If I boot my
laptop into the Ubuntu partition and try to pair it just fails to pair.
I'm very confident this is an issue exclusive to my Ubuntu machines my
Mac and Windows
@Konrad
Sorry for not being more specific I'm having the issues for the Bose
QC35 headphones.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620636
Title:
Fails to pair with Bose QC35 headphones
T
I am also seeing the identical issues as described above
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620636
Title:
Fails to pair with Bose QC35 headphones
To manage notifications about this bug
I am marking verification-done, as this fixes the issue for me on
xenial.
When running with the curtin build currently in xenial-updates
(/dev/vdb3 is used as physical volume for several lvm volumes):
root@ubuntu:/home/ubuntu# apt-cache policy curtin
curtin:
Installed: 0.1.0~bzr399-0u
I'm marking verification-done, as curtin successfully creates whole disk
fat partitions using the version in proposed. An example config file is
attached.
On system used for curtin pack:
# apt-cache policy curtin
curtin:
Installed: 0.1.0~bzr425-0ubuntu1~16.04.1
Candidate: 0.1
I can verify that the build in xenial-proposed resolves this bug using
the example config attached.
Running an installation using curtin packed on a system with the current curtin
release in xenial-updates installation fails.
Curtin release:
root@tmp:/tmp# apt-cache policy curtin
curtin:
Hi,
After looking into the autopkgtest failure reported in the puppet logs,
I am not sure if this is an error with puppet compatibility with apache
or an issue with the autopkgtest test bed used for running the tests, as
I had previously seen a failure (a slightly different one though), but
am no
Hi,
After looking into the autopkgtest failure reported in the puppet logs,
I am not sure if this is an error with puppet compatibility with apache
or an issue with the autopkgtest test bed used for running the tests, as
I had previously seen a failure (a slightly different one though), but
am no
Hi,
After looking into the autopkgtest failure reported in the puppet logs,
I am not sure if this is an error with puppet compatibility with apache
or an issue with the autopkgtest test bed used for running the tests, as
I had previously seen a failure (a slightly different one though), but
am no
Hi,
After looking into the autopkgtest failure reported in the puppet logs,
I am not sure if this is an error with puppet compatibility with apache
or an issue with the autopkgtest test bed used for running the tests, as
I had previously seen a failure (a slightly different one though), but
am no
Since this bug had been inactive for quite a while previously the
original reporter may no longer be following it.
I tested out the version in proposed, and can verify that the version in
proposed finds the samba logs correctly. Since the patch only adds an
additional rule to match the samba log f
Here's a debdiff for trusty that brings in the fix as it went into
upstream. Note that it is slightly different than the patch attached to
the bug.
A build including the this debdiff is available at:
https://launchpad.net/~wesley-wiedenmeier/+archive/ubuntu/test
** Patch
The fix in upstream was at revision 246:
https://sourceforge.net/p/logwatch/code/246/#diff-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010602
Title:
samba logs are not being reported in logwatc
Hi,
This was fixed in upsteam as of release 7.4.2, which is present in
Xenial. The fix is not present in Trusty though, so I will prepare a
debdiff including your patch as it was added by upstream for sru.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Hi Matthias,
Thanks for helping figure out what was going on with the differing results in
the test case.
Since the new debdiff contains the rest of the patch for the original issue
I'll go ahead and continue the sru process for that debdiff.
Hopefully the second issue with rewrite directives w
Hi,
I reran the verification using the build in trusty-proposed, and it
works nicely. Since I've verified twice and the original bug author has
verified the build that was in my ppa earlier, which was identical to
the one in trusty-proposed, I am confident that the version in trusty-
proposed fixe
Since a SRU for (LP: #1534538) was recently uploaded to trusty-proposed
using the same version string as the current debdiff, I have redone the
patch on top of the version of apache currently in trusty-proposed. The
updated debdiff is attached.
A package with the updated debdiff is currently build
Hi,
Sorry for the delay in getting the second part of the fix backported and
about the confusion over which commits from upstream should be
backported.
I have a updated debdiff that brings in the second part of the fix from
upstream at:
http://svn.apache.org/viewvc?view=revision&revision=1557641
The build of apache 2.4.7-1ubuntu4.14 in the ppa appears to work for me.
It would be good if the original bug reporter could test the build in the ppa
in order to verify it before it goes into trusty-proposed though, thanks.
Here is the test case I used:
root@ubuntu:~$ apt-cache show apache2 | gr
Here is the updated debdiff. A build is running with it, which I will
test soon. It will be available in ppa:wesley-wiedenmeier/test2
It uses the version number '2.4.7-1ubuntu4.14'. There is another sru
that I am working to get approved for apache2 that also uses
'ubuntu4.14'. If that one gets upl
There was recently a security update for apache2 that went in to trusty-
updates, so I need to remake the debdiff based off of the updated
version in trusty-proposed as the security update took the package
version that the above debdiff had. When that is done I will update the
version in ppa if any
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296835
Title:
status_of_proc lacks a "-p" in /etc/init.d/pptpd
To manage notific
The version in trusty-proposed looks like it fixes the issue.
ubuntu@ubuntu:~$ apt-cache show pptpd | grep Version
Version: 1.3.4+27+gddb30f8-1ubuntu1
ubuntu@ubuntu:~$ sudo /etc/init.d/pptpd start
ubuntu@ubuntu:~$ sudo /etc/init.d/pptpd status
* /usr/sbin/pptpd is not running
ubuntu@ubuntu:~$ ap
The updated package at version apache_2.4.7-1ubuntu4.14 does fix the
issue for me:
/etc/apache2/sites-available/alias.conf:
AliasMatch ^/alias-test/ /var/www/html/index.html
/var/www/html/index.html:
test
With current apache in trusty-updates:
ubuntu@ubuntu:/etc/apache2$ curl localhost/al
Assignee: Wesley Wiedenmeier (wesley-wiedenmeier) => (unassigned)
** Changed in: apache2 (Ubuntu Trusty)
Assignee: (unassigned) => Wesley Wiedenmeier (wesley-wiedenmeier)
** Changed in: apache2 (Ubuntu Trusty)
Status: Triaged => In Progress
--
You received this bug notificat
Hi,
Thanks for reviewing the patch, sorry I didn't notice the pending one in trusty
proposed.
There should be no regression potential for this patch, as it just removes an
incorrect strlen check.
I will update the debdiff with the regression potential field set and
based on the pending apache i
I confirm that the debdiff supplied does fix the bug. In case anyone
wants to test it, there is a build of it here:
https://launchpad.net/~wesley-wiedenmeier/+archive/ubuntu/tmp
Test case used to verify:
Config:
ubuntu@ubuntu:/etc/apache2$ cat sites-available/alias.conf
AliasMatch ^/alias
Here is a debdiff to pull in the patch from upstream. I am testing it
right now and should be able to confirm that it resolves the issue
shortly.
Since there was no testcase in the description, here is the testcase
from the bugzilla.redhat.com bug:
Steps to Reproduce:
# prepare test file.
echo "h
** Changed in: ntp (Ubuntu)
Assignee: Wesley Wiedenmeier (wesley-wiedenmeier) => (unassigned)
** Changed in: ntp (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi iulianpojar and stefandberg,
It appears that the trace you posted recently is actually a similar but
slightly different issue. Work on it is being tracked in (LP: 1562249):
https://bugs.launchpad.net/curtin/+bug/1562249
I will try to have a patch shortly, and work on getting it approved as a
This was reported on the debian bugtracker here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747146
It was patched at debian version 1.4.0-3
Attached is a debdiff to fix the issue in trusty.
There is a package built with the patch in a ppa here:
https://launchpad.net/~wesley-wiedenmeier
Before this is uploaded it would be good if anyone who has been
experienceing this bug could that the patched version resolves the issue
for them, thanks.
The updated deb is available here:
https://launchpad.net/~wesley-wiedenmeier/+archive/ubuntu/test2/+build/10037671
--
You received this bug
Since it looks like network-manager needs to pull in 'vlan' by default,
here is a debdiff that adds it to recommends.
It may make sense to write a patch that grays out menu entries for
network types which do not have the required deps installed, but this
may have to wait until later.
** Patch add
It looks to me like the patched version resolves the bug. If anyone else wants
to test before uploading there is a deb in my ppa here:
ppa:wesley-wiedenmeier/test2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Here's an updated debdiff to apply this patch, with better formatting
for the changelog entry
** Patch added: "fix_remoteip_proxy_match.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1511222/+attachment/4686910/+files/fix_remoteip_proxy_match.debdiff
--
You received this bug
Here is the debdiff to apply the patch in trusty. I will run through the
test case and verify that the patch works tomorrow.
** Patch added: "fix_remoteip_proxy_match.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1511222/+attachment/4680126/+files/fix_remoteip_proxy_match.deb
I don't see any sign that *I* sent you anything. I don't have the
"davidryman.com" domain.
Wesley
On 04/23/2016 11:23 PM, Peter Block wrote:
> Why would you send me weight loss spam in a message like that?
>
>
> On Sat, Apr 23, 2016 at 7:36 PM, davidryman wrote:
I modified the script that I wrote to try to reproduce this error and
was able to consistantly see IO errors when the script was added to the
cloud-config-archive being passed to an image. Instead of writing only
to either /dev/console or the real serial device which was /dev/ttyS0
here, each threa
Something interesting I noticed while looking into this is that when
xenial images are booted without "net.ifnames=0" the
/var/lib/cloud/instance/ directory is not populated. Even if no
datasource is provided for the image it should still create a blank
cloud-config.txt and the directory structure
I don't think that this is related to the cloud-final.service file
including StandardOutput=journal+console, the issue occurs in the same
situations as before with standard output being redirected only to
journal, or to console or to neither
--
You received this bug notification because you are a
I spent a while trying to reproduce this well:
- I tried many vm configurations running 'serial-shell-looper', both manually
and started by cloud-init but it didn't break
- I wrote a similar script using util.meta_log to see if the difference in
implementation between python open() and
Public bug reported:
KDE https://bugs.kde.org/show_bug.cgi?id=345973
The last comment is:
You must have libkf5notifications5 package version 5.10 or newer. If you have,
it might be another issue (although unlikely). If you don't, then please
update.
This bug is fixed in 5.10 of libkf5notifica
Public bug reported:
Preparing to install Lubuntu on uefi system with usb.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.25
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1
Virtual box crashed, that was normal.
Firefox crashed, that one is normal.
The one that is not normal crash is qaptwork2.0
The date of the crash is not consistent when the machine locked up.
I will try to get into SSH if it locks up, which I think wil be soon.
Because it is starting to have slugg
1 - 100 of 565 matches
Mail list logo
