[Bug 1575779] Re: hostnamectl fails under lxd unpriv container
** 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 fails under lxd unpriv container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575779] Re: hostnamectl fails under lxd unpriv container
** 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 fails under lxd unpriv container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598310] Re: Curtin block.get_blockdev_sector_size incorrectly assumes block._lsblock will return a dictionary with only a single entry
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-0ubuntu1~16.04.1
Candidate: 0.1.0~bzr399-0ubuntu1~16.04.1
root@ubuntu:/home/ubuntu# python3
Python 3.5.2 (default, Sep 10 2016, 08:21:44)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from curtin import block
>>> block.get_blockdev_sector_size("/dev/vdb3")
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/curtin/block/__init__.py", line
426, in get_blockdev_sector_size
[parent] = info
ValueError: too many values to unpack (expected 1)
When running with proposed (note that 4096 is actual sector size as advanced
format disk used):
root@ubuntu:/home/ubuntu# apt-cache policy curtin
curtin:
Installed: 0.1.0~bzr425-0ubuntu1~16.04.1
Candidate: 0.1.0~bzr425-0ubuntu1~16.04.1
root@ubuntu:/home/ubuntu# python3
Python 3.5.2 (default, Sep 10 2016, 08:21:44)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from curtin import block
>>> block.get_blockdev_sector_size("/dev/vdb3")
(4096, 4096)
** 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/1598310
Title:
Curtin block.get_blockdev_sector_size incorrectly assumes
block._lsblock will return a dictionary with only a single entry
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1598310/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597923] Re: curtin is unable to create whole disk fat/vfat formats
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.0~bzr425-0ubuntu1~16.04.1 Note that the failure that this bug was reported for seems to only affect trusty and precise, and the mkfs.vfat tool on xenial seems to write whole disk partitions without the -I flag. However, it is still more correct to use the flag as the expected behavior of mkfs.vfat is to refuse to partition without the flag. This fix should also be SRU'ed to trusty ** Attachment added: "conf.yaml" https://bugs.launchpad.net/curtin/+bug/1597923/+attachment/4756445/+files/conf.yaml ** 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/1597923 Title: curtin is unable to create whole disk fat/vfat formats To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1597923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597522] Re: curtin passes wrong args to mkfs when making filesystem on advanced format disks
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: Installed: 0.1.0~bzr399-0ubuntu1~16.04.1 Candidate: 0.1.0~bzr399-0ubuntu1~16.04.1 Failure: Unexpected error while running command. Command: ['mkfs.xfs', '-s', '1', '-f', '/dev/vdb2'] Exit code: 1 Reason: - Stdout: '' Stderr: 'unknown option -s 1\nUsage: mkfs.xfs\n/* blocksize */\t\t[-b log=n|size ... When curtin is packed with the release in proposed, installation works Curtin release: curtin: Installed: 0.1.0~bzr425-0ubuntu1~16.04.1 Candidate: 0.1.0~bzr425-0ubuntu1~16.04.1 ** Attachment added: "conf.yaml" https://bugs.launchpad.net/curtin/+bug/1597522/+attachment/4756350/+files/conf.yaml ** 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/1597522 Title: curtin passes wrong args to mkfs when making filesystem on advanced format disks To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1597522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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 longer able to. I currently can run the puppet autopkgtests on amd64 with no failures with -proposed enabled using the most recent trusty ephemeral '20161003_03:49'. A log of the a test run is attached. In the log at http://autopkgtest.ubuntu.com/packages/p/puppet/trusty/amd64/ it looks like something went wrong when trying to install puppet, so that may be the cause of the failure: autopkgtest [21:49:22]: apt-source puppet E: Command line option --only-source is not understood Since I do not have a way to reproduce the test failure at the moment, I am not sure if I can resolve the issue. ** Attachment added: "out" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+attachment/4753682/+files/out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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 longer able to. I currently can run the puppet autopkgtests on amd64 with no failures with -proposed enabled using the most recent trusty ephemeral '20161003_03:49'. A log of the a test run is attached. In the log at http://autopkgtest.ubuntu.com/packages/p/puppet/trusty/amd64/ it looks like something went wrong when trying to install puppet, so that may be the cause of the failure: autopkgtest [21:49:22]: apt-source puppet E: Command line option --only-source is not understood Since I do not have a way to reproduce the test failure at the moment, I am not sure if I can resolve the issue. ** Attachment added: "out" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+attachment/4753683/+files/out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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 longer able to. I currently can run the puppet autopkgtests on amd64 with no failures with -proposed enabled using the most recent trusty ephemeral '20161003_03:49'. A log of the a test run is attached. In the log at http://autopkgtest.ubuntu.com/packages/p/puppet/trusty/amd64/ it looks like something went wrong when trying to install puppet, so that may be the cause of the failure: autopkgtest [21:49:22]: apt-source puppet E: Command line option --only-source is not understood Since I do not have a way to reproduce the test failure at the moment, I am not sure if I can resolve the issue. ** Attachment added: "out" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+attachment/4753680/+files/out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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 longer able to. I currently can run the puppet autopkgtests on amd64 with no failures with -proposed enabled using the most recent trusty ephemeral '20161003_03:49'. A log of the a test run is attached. In the log at http://autopkgtest.ubuntu.com/packages/p/puppet/trusty/amd64/ it looks like something went wrong when trying to install puppet, so that may be the cause of the failure: autopkgtest [21:49:22]: apt-source puppet E: Command line option --only-source is not understood Since I do not have a way to reproduce the test failure at the moment, I am not sure if I can resolve the issue. ** Attachment added: "out" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+attachment/4753681/+files/out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] Re: samba logs are not being reported in logwatch
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 files and does not remove the old rule, there is no real regression potential, other than users seeing output samba messages in their logwatch output that they had not been seeing before. Verification procedure (note that samba was not configured and was did not start. the failure messages from it were still picked up by logwatch with the fix applied though. note also that if logwatch not matching the samba startup failure messages is considered a bug, it is separate from logwatch not reporting the samba logs at all): root@unissuable-cade:~# apt-cache show logwatch | grep Version Version: 7.4.0+svn20130529rev144-1ubuntu1 root@unissuable-cade:~# sudo apt-get install samba root@unissuable-cade:~# sudo service samba restart nmbd stop/waiting nmbd start/running, process 12562 smbd stop/waiting smbd start/running, process 12574 stop: Unknown instance: samba-ad-dc start/running, process 12589 root@unissuable-cade:~# logwatch --detail high --logdir /var/log/ --range all --service samba # no output, but /var/log/samba/log.%m has contents from restarting root@unissuable-cade:/usr/share/logwatch/scripts# apt-cache show logwatch | grep Version Version: 7.4.0+svn20130529rev144-1ubuntu1.1 Version: 7.4.0+svn20130529rev144-1ubuntu1 root@unissuable-cade:~# logwatch --detail high --logdir /var/log/ --range all --service samba ### Logwatch 7.4.0 (05/29/13) Processing Initiated: Tue Sep 27 17:51:44 2016 Date Range Processed: all Detail Level of Output: 10 Type of Output/Format: stdout / text Logfiles for Host: unissuable-cade ## - samba Begin **Unmatched Entries** ../lib/util/become_daemon.c:111(exit_daemon) STATUS=daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details, error code 22 : 3 Time(s) ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'nmbd' finished starting up and ready to serve connections : 2 Time(s) ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'smbd' finished starting up and ready to serve connections : 2 Time(s) ../source4/smbd/server.c:477(binary_smbd_main) At this time the 'samba' binary should only be used for either: 'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote' You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks : 3 Time(s) -- samba End - ## Logwatch End # ** 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/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] Re: samba logs are not being reported in logwatch
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 added: "fix_match_samba_logs.debdiff" https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+attachment/4726184/+files/fix_match_samba_logs.debdiff -- 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 logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] Re: samba logs are not being reported in logwatch
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 logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010602] Re: samba logs are not being reported in logwatch
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/logwatch/+bug/1010602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
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 will be fixed by upstream soon. If you don't already have a bug open on the upstream bugtracker it would be good to open one, then hopefully we can get the fix into debian and ubuntu. Since you have a patch for the .htaccess bug, upstream should be willing to accept it. It probably wouldn't be possible to sru a patch before it is accepted into upstream, but once it is it should be fine to do. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394403 Title: RewriteRule of "^$" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1394403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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 fixes the patch. I'm going to mark verification-done. Here's the verification from trusty proposed: ubuntu@ubuntu:~$ apt-cache show apache2 | grep Version Version: 2.4.10-1ubuntu1.1~ubuntu14.04.1 Version: 2.4.7-1ubuntu4.13 Version: 2.4.7-1ubuntu4 ubuntu@ubuntu:/etc/apache2$ cat sites-enabled/alias.conf AliasMatch ^/alias-test/ /var/www/html/index.html ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/010203040506070809101112 test ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/01020304050607080910111213 curl: (52) Empty reply from server ubuntu@ubuntu:/etc/apache2$ apt-cache show apache2 | grep Version Version: 2.4.10-1ubuntu1.1~ubuntu14.04.1 Version: 2.4.7-1ubuntu4.14 Version: 2.4.7-1ubuntu4.13 Version: 2.4.7-1ubuntu4 ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/010203040506070809101112 test ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/01020304050607080910111213 test ** 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/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511222] Re: Incorrect trusted proxy match test in mod_remoteip
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 building in ppa:wesley- wiedenmeier/test2 if anyone would like to test it out. Since I have already run through a test case twice for this patch, and the patch itself is the same for each version, I will not redo the test case for this version, as it should come out the same. If any users would like to test the patch before it is uploaded, it is available in ppa. Thanks ** Patch added: "second_updated_fix_remoteip_proxy_match.debdiff" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1511222/+attachment/4711974/+files/second_updated_fix_remoteip_proxy_match.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511222 Title: Incorrect trusted proxy match test in mod_remoteip To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1511222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
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 Note though, that the modification to include/ap_mmn.h from that revision was not included in the attached debdiff. The change to that file was only to increment the minor version number for the modules included in this build. Since it was a bump to minor number there is no major incompatibility. Since there have been many changes to upstream between the last minor increment in module version number here, it did not make sense to modify the version number as it had been modified in the upstream revision. If it turns out that it would be good to modify the minor version in another way, please let me know and I will make that change. Before I had tested the version of apache2 currently in trusty-updates with the provided test case and it appeared to me that everything was working as expected. Once this package has built I will repeat this test and will see if I can update the testcase slightly to show a difference in behavior between apache with this fix and the version with the older fix if none is immediately obvious. The package is building in a ppa at: ppa:wesley-wiedenmeier/test If anyone would like to test with the most recent debdiff that would be appreciated. Thanks ** Patch added: "fix_rewrite_rule_update.debdiff" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1394403/+attachment/4707966/+files/fix_rewrite_rule_update.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394403 Title: RewriteRule of "^$" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1394403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511222] Re: Incorrect trusted proxy match test in mod_remoteip
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 | grep Version
Version: 2.4.7-1ubuntu4.13
root@ubuntu:/etc/apache2# a2enmod rewrite remoteip
root@ubuntu:~$ cat /etc/apache2/sites-available/remoteip.conf
RemoteIPHeader X-Forwarded-For
RemoteIPTrustedProxy 127.0.0.1
RewriteEngine on
RewriteRule ^/?(.*) http://test.invalid/%{REMOTE_ADDR} [R=301,L]
root@ubuntu:/home/ubuntu# a2dissite 000-default
root@ubuntu:/home/ubuntu# a2ensite remoteip
root@ubuntu:/home/ubuntu# service apache2 restart
root@ubuntu:/home/ubuntu# curl -vH 'X-Forwarded-For: 1.2.3.4' http://127.0.0.1
2>&1 | grep Location
< Location: http://test.invalid/1.2.3.4
root@ubuntu:/home/ubuntu# curl -vH 'X-Forwarded-For: 5.6.7.8, 1.2.3.4'
http://127.0.0.1 2>&1 | grep Location
< Location: http://test.invalid/5.6.7.8
root@ubuntu:/home/ubuntu# apt-add-repository ppa:wesley-wiedenmeier/test2
root@ubuntu:/home/ubuntu# apt-get update
root@ubuntu:/home/ubuntu# apt-get install apache2
root@ubuntu:/home/ubuntu# apt-cache show apache2 | grep Version
Version: 2.4.7-1ubuntu4.14
root@ubuntu:/home/ubuntu# service apache2 restart
root@ubuntu:/home/ubuntu# curl -vH 'X-Forwarded-For: 1.2.3.4' http://127.0.0.1
2>&1 | grep Location
< Location: http://test.invalid/1.2.3.4
root@ubuntu:/home/ubuntu# curl -vH 'X-Forwarded-For: 5.6.7.8, 1.2.3.4'
http://127.0.0.1 2>&1 | grep Location
< Location: http://test.invalid/1.2.3.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511222
Title:
Incorrect trusted proxy match test in mod_remoteip
To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1511222/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511222] Re: Incorrect trusted proxy match test in mod_remoteip
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 uploaded first I will update this patch again. ** Attachment added: "updated_fix_remoteip_proxy_match.debbdiff" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1511222/+attachment/4707515/+files/updated_fix_remoteip_proxy_match.debbdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511222 Title: Incorrect trusted proxy match test in mod_remoteip To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1511222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511222] Re: Incorrect trusted proxy match test in mod_remoteip
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 anyone wants to test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511222 Title: Incorrect trusted proxy match test in mod_remoteip To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1511222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296835] Re: status_of_proc lacks a "-p" in /etc/init.d/pptpd
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pptpd/+bug/1296835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296835] Re: status_of_proc lacks a "-p" in /etc/init.d/pptpd
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:~$ apt-cache show pptpd | grep Version Version: 1.3.4+27+gddb30f8-1ubuntu1.1 ubuntu@ubuntu:~$ sudo /etc/init.d/pptpd start ubuntu@ubuntu:~$ sudo /etc/init.d/pptpd status * pptpd is running -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pptpd/+bug/1296835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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/alias-test/010203040506070809101112 test ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/01020304050607080910111213 curl: (52) Empty reply from server After update to apache 2.4.7-1ubuntu4.14: ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/010203040506070809101112 test ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/01020304050607080910111213 test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
I have rebased the patch on the newest version in trusty updates apache2_2.4.7-1ubuntu4.13, which includes the security fix. The updated debdiff is attached. If anyone would like to test there is a .deb with the updated patch building in in the ppa at: ppa:wesley-wiedenmeier/tmp I will confirm that the new version of the patch works again once the package has built. ** Patch added: "fix_aliasmatch_long_uri.debdiff" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+attachment/4704309/+files/fix_aliasmatch_long_uri.debdiff ** Changed in: apache2 (Ubuntu) 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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 in trusty-proposed and have it posted here this afternoon. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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-test/ /var/www/html/index.html With old apache: ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/short_uri TEST ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/very_l ong_uri curl: (52) Empty reply from server ubuntu@ubuntu:/etc/apache2$ With new apache: ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/short_uri TEST ubuntu@ubuntu:/etc/apache2$ curl localhost/alias-test/very_l ong_uri TEST -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534538] Re: AliasMatch directive does not accept long URI
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 "hello" > /var/www/html/index.html # add config to apache echo "AliasMatch ^/alias-test/ /var/www/html/index.html" > /etc/httpd/conf.modules.d/02-alias-test.conf # (re)start httpd systemctl restart httpd.service Actual results: # When I request short URI, the response is good as follow: [takayuki@localhost ~]$ wget -t1 -O - -S -v http://127.0.0.1/alias-test/short_uri --2014-07-16 14:04:38-- http://127.0.0.1/alias-test/short_uri Connecting to 127.0.0.1:80... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Date: Wed, 16 Jul 2014 05:04:38 GMT Server: Apache/2.4.9 (Fedora) Last-Modified: Wed, 16 Jul 2014 04:49:10 GMT ETag: "13-4fe483eb8a9d6" Accept-Ranges: bytes Content-Length: 19 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html; charset=UTF-8 Length: 19 [text/html] Saving to: 'STDOUT' 0% [ ] 0 --.-K/s hello 100%[=>] 19 --.-K/s in 0s 2014-07-16 14:04:38 (2.03 MB/s) - written to stdout [19/19] # When I request log URI, the connection is closed and Apache logged error as follow: [takayuki@localhost ~]$ wget -t1 -O - -S -v http://127.0.0.1/alias-test/very_looong_uri --2014-07-16 14:07:40-- http://127.0.0.1/alias-test/very_looong_uri Connecting to 127.0.0.1:80... connected. HTTP request sent, awaiting response... No data received. Giving up. [root@localhost takayuki]# tail /var/log/httpd/error_log [crit] Memory allocation failed, aborting process. [Wed Jul 16 14:03:17.231921 2014] [core:notice] [pid 21808] AH00052: child pid 21809 exit signal Aborted (6) [crit] Memory allocation failed, aborting process. [Wed Jul 16 14:03:23.239149 2014] [core:notice] [pid 21808] AH00052: child pid 21812 exit signal Aborted (6) [crit] Memory allocation failed, aborting process. [Wed Jul 16 14:07:40.487959 2014] [core:notice] [pid 21808] AH00052: child pid 21945 exit signal Aborted (6) ** Patch added: "fix_aliasmatch_long_uri.debdiff" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+attachment/4691634/+files/fix_aliasmatch_long_uri.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534538 Title: AliasMatch directive does not accept long URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1534538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582767] Re: apparmor permissions missing for winbind
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1582767 Title: apparmor permissions missing for winbind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1582767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263181] Re: curtin discovers HP /dev/cciss/c0d0 incorrectly
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 SRU to Xenial and Trusty, sorry about the inconvenience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263181 Title: curtin discovers HP /dev/cciss/c0d0 incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1263181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296835] Re: status_of_proc lacks a "-p" in /etc/init.d/pptpd
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/+archive/ubuntu/test ** Bug watch added: Debian Bug tracker #747146 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747146 ** Patch added: "fix_status_check.debdiff" https://bugs.launchpad.net/ubuntu/+source/pptpd/+bug/1296835/+attachment/4688087/+files/fix_status_check.debdiff ** Changed in: pptpd (Ubuntu) Assignee: (unassigned) => Wesley Wiedenmeier (wesley-wiedenmeier) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pptpd/+bug/1296835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511222] Re: Incorrect trusted proxy match test in mod_remoteip
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511222 Title: Incorrect trusted proxy match test in mod_remoteip To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1511222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519120] Re: Xenial: VLAN interfaces don't work until after a reboot
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 added: "add_vlan.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1519120/+attachment/4688034/+files/add_vlan.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519120 Title: Xenial: VLAN interfaces don't work until after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1519120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511222] Re: Incorrect trusted proxy match test in mod_remoteip
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.net/bugs/1511222 Title: Incorrect trusted proxy match test in mod_remoteip To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1511222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511222] Re: Incorrect trusted proxy match test in mod_remoteip
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511222 Title: Incorrect trusted proxy match test in mod_remoteip To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1511222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511222] Re: Incorrect trusted proxy match test in mod_remoteip
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.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511222 Title: Incorrect trusted proxy match test in mod_remoteip To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1511222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
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 thread writes to both and calls .flush() on one after the other. Without writing to both /dev/console and /dev/ttyS0 I have not seen any IOErrors, so I believe that this may have something to do with the mechanism for /dev/console being forwarded into /dev/ttyS0. I have not yet been able to cause an IO error using this script on its own, only when it is being run by cloud-init. I think this might be because of the cloud-final.service file specifying output from cloud- init to be written to console as well, causing another simultaneous write. I will work on trying to modify this script so that it can trigger the error when being run on its own as well. I think that in the original error occuring during curtin vmtests some other process may have been writing to /dev/ttyS0 as cc_ssh_authkeys was writing to /dev/console via util.multi_log, causing this error to occur With this script in cloud-init userdata I have seen at least one or two OSErrors in serial output each time the system has been tested. New script: http://paste.ubuntu.com/15906498/ Example serial.log output from launch framework similar to curtin vmtests: http://paste.ubuntu.com/15906571/ There is a well formatted stacktrace on line 6730 and several others higher up that are difficult to read -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
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 in /var/lib/cloud/ should be set up, so I think that there is a bug somewhere else in cloud-init causing this. I think there is a good chance that this is what's triggering the issue with cc_ssh_authkey_fingerprints we're seeing here, but I am not sure how yet. I want to try to figure out why this is happening though, because in some conditions, like in curtin vmtests XenialTestNetwork everything is working correctly. The issue with /var/lib/cloud/instance/ seems to occur both with current cloud-init and with cloud-init at revision 1188, so it is not linked to the new networking code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
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 shell piping would make a difference. I wasn't able to find anything useful though. http://paste.ubuntu.com/15843875/ - I was able to reproduce about 9 times out of 10 using XenialTestBasic with no modifications. After removing most of the functionality of the test other than basic booting (no curtin cmd, no curtin archive, no extra disks), it still failed just as reliably. There were still occasional cases where there was no failure though - Since these failures have been occurring much more recently, I reverted the net.ifnames=0 removal and ran vmtests several times, and did not see any failures. I enabled and disabled this parameter many times to make sure, but it appears that this issue appears almost always with ifnames enabled and never with them disabled, suggesting that somehow that I haven't figured out yet naming of network devices is shifting timing enough that it can toggle this error on and off - I was able to reproduce it just as often using a modified version of the cloud-init vmtests, using both a cloud-init deb built from the current revision of cloud-init and a deb built from cloud-init at revision 1188, before the new networking code was merged in. In both versions, this error almost always occurred when running with ifnames enabled and never occurred when running with ifnames disabled. I'm not really sure how to reproduce this error on a small scale yet. I am going to try to figure out what could be running concurrently with cc_ssh_authkey_fingerprints and see if I can figure anything else out from there. I haven't yet tried disabling StandardOutput=journal+console in cloud-final.service, but I will give that a try as well, although it is already present in wily and wily does not seem to have this issue The only idea I have so far for underlying cause is flow control on /dev/console. Since serial console is being forwarded to a file over ipmi by qemu and is write only it may be possible that somehow something expects to read from there (maybe agetty?) and flow control is causing a block. I'm not sure if that makes sense though. The main thing that suggests that is a series of bugs in several different mailing lists about syslog-ng writing directly to /dev/console causing hangs in some situations such as when traffic from /dev/console is being forwarded to a device that temporarily goes offline, causing write to block. http://comments.gmane.org/gmane.comp.syslog-ng/10561 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
Thanks for the test case, that works really well. Sorry that the next commit in upstream was not included in the SRU, I should have caught that. At the version that's in the repos now I do see a change in behaviour in the log files between when 'DirectoryCheckHandler Off' is set and when it is set on. With DirectoryCheckHandler On I get: http://paste.ubuntu.com/12551255 And with it set to Off I get: http://paste.ubuntu.com/12551264 So to me it looks like the issue is resolved, but I will prepare a new debdiff with the rest of the upstream fix tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394403 Title: RewriteRule of "^$" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1394403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Thank you for sponsoring, I will open a bug report on their tracker and link to this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
I can confirm that the package in trusty-proposed resolves the issue for me in a trusty vm with the default values set. I think it should be good to go into trusty-updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394403 Title: RewriteRule of "^$" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1394403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
Awesome, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394403 Title: RewriteRule of "^$" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1394403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
** Description changed: [Test Case] Setup Apache 2.4.7 * mod_rewrite * mod_ajp * mod_dir Tomcat * Listening on Port 9001 Apache with a .htaccess in the example.net VirtualHost - RewriteEngine On - RewriteRule ^(.*)$ ajp://localhost:9001/$1 [P] - + RewriteEngine On + RewriteRule ^(.*)$ ajp://localhost:9001/$1 [P] Expected: Return from Tomcat - HTTP Status 404 - / + HTTP Status 404 - / Reality: Return from Tomcat - HTTP Status 404 - /index.html + HTTP Status 404 - /index.html - - Workaround for this particular setup was to either disable mod_dir or disable DirectoryIndex in .htaccess. + Workaround for this particular setup was to either disable mod_dir or + disable DirectoryIndex in .htaccess. Or on VirtualHost context use ProxyPass. - ProxyPass / ajp://localhost:9001/ - ProxyPassReverse / ajp://localhost:9001/ - + ProxyPass / ajp://localhost:9001/ + ProxyPassReverse / ajp://localhost:9001/ [Impact] With DirectoryIndex disabled: - [Thu Apr 30 13:55:18.761066 2015] [rewrite:trace3] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] strip per-dir prefix: /home/www-data/example.net/ -> + [Thu Apr 30 13:55:18.761066 2015] [rewrite:trace3] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] strip per-dir prefix: /home/www-data/example.net/ -> [Thu Apr 30 13:55:18.761191 2015] [rewrite:trace3] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] applying pattern '^(.*)$' to uri '' [Thu Apr 30 13:55:18.761215 2015] [rewrite:trace2] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] rewrite '' -> 'ajp://localhost:9001/' [Thu Apr 30 13:55:18.761232 2015] [rewrite:trace2] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] escaped URI in per-dir context for proxy, ajp://localhost:9001/ -> ajp://localhost:9001/ [Thu Apr 30 13:55:18.761245 2015] [rewrite:trace2] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] forcing proxy-throughput with ajp://localhost:9001/ [Thu Apr 30 13:55:18.761259 2015] [rewrite:trace1] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] go-ahead with proxy request proxy:ajp://localhost:9001/ [OK] With DirectoryIndex enabled: - [Thu Apr 30 13:58:37.954876 2015] [rewrite:trace3] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] strip per-dir prefix: /home/www-data/example.net/ -> + [Thu Apr 30 13:58:37.954876 2015] [rewrite:trace3] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] strip per-dir prefix: /home/www-data/example.net/ -> [Thu Apr 30 13:58:37.954930 2015] [rewrite:trace3] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] applying pattern '^(.*)$' to uri '' [Thu Apr 30 13:58:37.954947 2015] [rewrite:trace2] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] rewrite '' -> 'ajp://localhost:9001/' [Thu Apr 30 13:58:37.954959 2015] [rewrite:trace2] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] escaped URI in per-dir context for proxy, ajp://localhost:9001/ -> ajp://localhost:9001/ [Thu Apr 30 13:58:37.954968 2015] [rewrite:trace2] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] forcing proxy-throughput with ajp://localhost:9001/ [Thu Apr 30 13:58:37.954977 2015] [rewrite:trace1] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7
[Bug 1478149] Re: python-tornado tests fail against python3.5
Updated debdiff with LP: #1478149 in changelog ** Attachment added: "wily-debdiff-updated" https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1478149/+attachment/4452185/+files/wily-debdiff-updated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478149 Title: python-tornado tests fail against python3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1478149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1478149] Re: python-tornado tests fail against python3.5
** Changed in: python-tornado (Ubuntu Wily) Assignee: Wesley Wiedenmeier (wesley-wiedenmeier) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478149 Title: python-tornado tests fail against python3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1478149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1478149] Re: python-tornado tests fail against python3.5
Attaching a debdiff that applies the fixes from upstream ** Attachment added: "wily-debdiff" https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1478149/+attachment/4447431/+files/wily-debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478149 Title: python-tornado tests fail against python3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1478149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1478149] Re: python-tornado tests fail against python3.5
Upstream has fixed this here: https://github.com/tornadoweb/tornado/commit/2971e857104f8d02fa9107a0e13f50170eb4f30d ** Changed in: python-tornado (Ubuntu Wily) Assignee: (unassigned) => Wesley Wiedenmeier (wesley-wiedenmeier) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478149 Title: python-tornado tests fail against python3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1478149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
Replaced the debdiff with one that uses the fix from apache 2.4 https://github.com/apache/httpd/commit/f0529e54b8d889322b5113eb623e263556bfa28e ** Patch removed: "trusty-sru-debdiff" https://bugs.launchpad.net/ubuntu/trusty/+source/apache2/+bug/1394403/+attachment/4445979/+files/trusty-sru-debdiff ** Attachment added: "trusty-sru-debdiff" https://bugs.launchpad.net/ubuntu/trusty/+source/apache2/+bug/1394403/+attachment/4447223/+files/trusty-sru-debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394403 Title: RewriteRule of "^$" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1394403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
Updated Description for SRU proposal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394403 Title: RewriteRule of "^$" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1394403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394403] Re: RewriteRule of "^$" is broken
Attaching debdiff with patch applied. ** Attachment added: "trusty-sru-debdiff" https://bugs.launchpad.net/ubuntu/trusty/+source/apache2/+bug/1394403/+attachment/4445979/+files/trusty-sru-debdiff ** Description changed: + [Test Case] + + Setup + Apache 2.4.7 + * mod_rewrite + * mod_ajp + * mod_dir + + Tomcat + * Listening on Port 9001 + + Apache with a .htaccess in the example.net VirtualHost + + RewriteEngine On + RewriteRule ^(.*)$ ajp://localhost:9001/$1 [P] + + + Expected: + Return from Tomcat + + HTTP Status 404 - / + + Reality: + Return from Tomcat + + HTTP Status 404 - /index.html + + + Workaround for this particular setup was to either disable mod_dir or disable DirectoryIndex in .htaccess. + + Or on VirtualHost context use ProxyPass. + + ProxyPass / ajp://localhost:9001/ + ProxyPassReverse / ajp://localhost:9001/ + + + [Impact] + + With DirectoryIndex disabled: + + [Thu Apr 30 13:55:18.761066 2015] [rewrite:trace3] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] strip per-dir prefix: /home/www-data/example.net/ -> + [Thu Apr 30 13:55:18.761191 2015] [rewrite:trace3] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] applying pattern '^(.*)$' to uri '' + [Thu Apr 30 13:55:18.761215 2015] [rewrite:trace2] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] rewrite '' -> 'ajp://localhost:9001/' + [Thu Apr 30 13:55:18.761232 2015] [rewrite:trace2] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] escaped URI in per-dir context for proxy, ajp://localhost:9001/ -> ajp://localhost:9001/ + [Thu Apr 30 13:55:18.761245 2015] [rewrite:trace2] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] forcing proxy-throughput with ajp://localhost:9001/ + [Thu Apr 30 13:55:18.761259 2015] [rewrite:trace1] [pid 31422] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38052] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb50a0/initial] [perdir /home/www-data/example.net/] go-ahead with proxy request proxy:ajp://localhost:9001/ [OK] + + + With DirectoryIndex enabled: + + [Thu Apr 30 13:58:37.954876 2015] [rewrite:trace3] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] strip per-dir prefix: /home/www-data/example.net/ -> + [Thu Apr 30 13:58:37.954930 2015] [rewrite:trace3] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] applying pattern '^(.*)$' to uri '' + [Thu Apr 30 13:58:37.954947 2015] [rewrite:trace2] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] rewrite '' -> 'ajp://localhost:9001/' + [Thu Apr 30 13:58:37.954959 2015] [rewrite:trace2] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] escaped URI in per-dir context for proxy, ajp://localhost:9001/ -> ajp://localhost:9001/ + [Thu Apr 30 13:58:37.954968 2015] [rewrite:trace2] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] forcing proxy-throughput with ajp://localhost:9001/ + [Thu Apr 30 13:58:37.954977 2015] [rewrite:trace1] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb10a0/initial] [perdir /home/www-data/example.net/] go-ahead with proxy request proxy:ajp://localhost:9001/ [OK] + [Thu Apr 30 13:58:37.955023 2015] [rewrite:trace3] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb30a0/subreq] [perdir /home/www-data/example.net/] strip per-dir prefix: /home/www-data/example.net/index.html -> index.html + [Thu Apr 30 13:58:37.955036 2015] [rewrite:trace3] [pid 31419] mod_rewrite.c(468): [client XXX.XXX.XXX.XXX:38156] XXX.XXX.XXX.XXX - - [example.net/sid#7fc6ddd849f8][rid#7fc6ddcb30a0/subreq] [perdir /home/www-data/example.net/] applying pattern '^(.*)$' to uri 'in
[Bug 1394403] Re: RewriteRule of "^$" is broken
** Changed in: apache2 (Ubuntu Trusty) Assignee: (unassigned) => Wesley Wiedenmeier (wesley-wiedenmeier) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394403 Title: RewriteRule of "^$" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1394403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
We should get sign off on this from the ubuntu-devel mailing list before making this change, as it changes behaviour. The new behaviour makes sense, as there does not seem to be an advantage to blanking the screen like this, but there might be some people who object -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Disabled blank screen in /etc/kbd/config ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/869017/+attachment/4439243/+files/patch ** Package changed: console-setup (Ubuntu) => kbd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Wesley Wiedenmeier (wesley-wiedenmeier) ** Changed in: console-setup (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/869017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 755198] Re: gnome-terminal stops echoing input
As Dave Gilbert said in the previous comment this is because echoing input is disabled so someone cannot read your password from behind you. This is not really a bug, this is expected behavior. To fix this simply type "stty echo" blindly into the terminal and press enter, and echoing input will be re-enabled. ** Changed in: ecryptfs-utils (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/755198 Title: gnome-terminal stops echoing input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/755198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 970994] Re: ecryptfs-migrate-home fails to complete is there are files with really long names
Could you please give a little more information, such as how long the filenames are, and how you have found that this fails. Also, you say that the files get encrypted, so does the encryption work properly and mounting work later, and it is just a lack of messages that you are talking about, or is the encrypted directory not mounting properly. ** Changed in: ecryptfs-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/970994 Title: ecryptfs-migrate-home fails to complete is there are files with really long names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/970994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001933] Re: ecryptfs-recover-private reports success even when MOUNT passphrase is wrong
Confirmed, when using ecryptfs-recover-private, answering no to "Do you know your LOGIN passphrase?" and being prompted for mount passphrase, inputting a wrong passphrase still results in Success! message, and encrypted filenames which cannot be read appear in the /tmp mount directory. ** Changed in: ecryptfs-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001933 Title: ecryptfs-recover-private reports success even when MOUNT passphrase is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1001933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936093] Re: Access-Your-Private-Data.desktop is not executable
The problem is the permissions on the .desktop file do not include execute permissions. A quick and easy solution for you would be to run "sudo chmod a+x /usr/share/ecryptfs-utils/ecryptfs-mount- private.desktop". When the .deb is downloaded and extracted, the file in usr/share/ecryptfs-utils/ecryptfs-mount-private.desktop has no execute permissions for any users, where it should have execute permissions for all users. ** Changed in: ecryptfs-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936093 Title: Access-Your-Private-Data.desktop is not executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/936093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
